ngircd with make http://git.nakidai.ru/ngircd/atom?h=rel-19.1 2012-03-19T18:19:58+00:00 2012-03-19T18:19:58+00:00 Alexander Barton alex@barton.de 2012-03-19T18:19:58+00:00 urn:sha1:fbaa751da824d0dd2a58086d2cec860cc88afa1d 2012-03-16T12:55:00+00:00 Alexander Barton alex@barton.de 2012-03-16T12:55:00+00:00 urn:sha1:06b63278754464792529ee0594dc218fa02b4c44 2012-03-12T21:27:55+00:00 Alexander Barton alex@barton.de 2012-03-12T21:27:55+00:00 urn:sha1:0d9740b9fa1a432d35f73fafa7fb2ecd9a435502 This fixes the following warning with gcc 4.6.3.: irc-mode.c: In function "Channel_Mode": irc-mode.c:947:26: error: "list" may be used uninitialized in this function irc-mode.c:884:25: error: "list" may be used uninitialized in this function (The variable has never been used uninitialized, so don't worry) 2012-03-12T10:02:17+00:00 Alexander Barton alex@barton.de 2012-03-12T10:02:17+00:00 urn:sha1:e9be3334d1f0a40e44aac7754d828a4ce28a94b7 Thanks to Christoph Biedl for reporting this! 2012-03-12T08:49:24+00:00 Alexander Barton alex@barton.de 2012-03-12T08:49:24+00:00 urn:sha1:0ae74ceaedef2583c333b7cf2a95802009d7707e Thanks to Götz Hoffart! 2012-03-12T08:47:19+00:00 Alexander Barton alex@barton.de 2012-03-12T08:47:19+00:00 urn:sha1:17ffda1c8a06855adb7a411734b1f7f8cc28d497 Thanks to Christoph Biedl. 2012-03-05T21:29:53+00:00 Alexander Barton alex@barton.de 2012-03-05T21:29:53+00:00 urn:sha1:0de11ead3663a1248ae0f0f97a2896845774a7d4 2012-03-05T20:30:38+00:00 Alexander Barton alex@barton.de 2012-03-05T20:26:03+00:00 urn:sha1:9d486db460c05c24e3a6b3264529a10f968cce2f 2012-03-03T17:53:03+00:00 Christoph Biedl ngircd.anoy@manchmal.in-ulm.de 2012-03-03T17:53:03+00:00 urn:sha1:257fe922d2c2ee822c372bc5b979075271915553 When * building the ngircd Debian package (on Linux at least) and * using the sbuild build system, the command "ps -af" does not include the commands running inside the sbuild system. Therefore, start-server.sh will report a fail as getpid.sh cannot not find the ./T-ngircd1 just started although it's actually running. This results in a funny build log ... starting server 1 ... failure! FAIL: start-server1 running connect-test ... ok. PASS: connect-test The self-test of getpid.sh however will likely succeed as it's happy if it sees any process with "sh" somewhere in the name. Things go downhill from there. The confusing things are: * The alternative cowbuilder/pbuilder does not have this problem. * The alternative usage "ps ax" does fine. So, as a quick hack, the patch attached adds another switch to getpid.sh. 2012-03-02T08:41:13+00:00 Alexander Barton alex@barton.de 2012-03-02T08:41:13+00:00 urn:sha1:1068f883779ad9b8bf3e1e1b8234781e4223761d Start "regular" logging not until the configuration file has been read in and "SyslolgFacility" is set, and log all configuration errors using the generic "daemon" facility. So if there are no configuration errors, logging starts right after parsing the configuration and we log the configuration file used _after_ reading it. But this is no problem because every configuration error message includes the configuration file name as well. (The "double hello" has been introduced by commit 3641e5110952)