Hello!
I just released the first „bug fix release“ for ngIRCd 19, named „19.1“. You can grab it on the usual locations, see below.
All changes are cosmetic (fixed typos in comments and log messages) or fix our build system, there have been no functional changes – so if you built and installed ngIRCd 19 successfully, there is no big reason to update. But feel free to do so anyway :-)
Please see the NEWS and ChangeLog files for all the glory details:
- <http://ngircd.barton.de/doc/NEWS>
- <http://ngircd.barton.de/doc/ChangeLog>
You can find more information on our homepage at <http://ngircd.barton.de/> and its mirror <http://ngircd.berlios.de/>. The primary download locations are:
- <ftp://ftp.berlios.de/pub/ngircd/>
- <http://ngircd.barton.de/pub/ngircd/>
Regards
Alex
Hi List Readers!
„We proudly present ngIRCd 19!“ – so here it is, the next stable release of ngIRCd!
There have been a few last fixes since the release candidate, for example the „SyslogFacility“ configuration variable should really work now and you can use GCC 2.7.2 again to build it [yeah, I know, who cares – but indeed a few do, including me ;-)].
Besides these fixes, ngIRCd 19 is the most usable release in combination with Anope IRC services ever: lots of enhancements and fixes went in, in addition to an updated Anope protocol module that works with Anope 1.9.6 released in early February (see included ./doc/Services.txt and ./contrib/Anope/README files for details).
The flood protection and „abuse prevention behavior“ has been greatly enhanced, for example by introducing new limits for channel ban and invite lists (MODE +b/+I) and other list replies (LIST, WHO, WHOIS, WHOWAS). And there are new commands (like GLINE and KLINE), new user modes (R, C) and channel modes (r, R), and channel exception lists (e) have been implemented as well. Lots of commands have been enhanced to better follow the RFC-specified and/or well known syntax and behavior (MODE, LINKS, WHO, LUSERS, …).
Please read the NEWS and ChangeLog files for the whole story:
- <http://ngircd.barton.de/doc/NEWS>
- <http://ngircd.barton.de/doc/ChangeLog>
You can find more information on our homepage at <http://ngircd.barton.de/> and its mirror <http://ngircd.berlios.de/>. The primary download locations are:
- <ftp://ftp.berlios.de/pub/ngircd/>
- <http://ngircd.barton.de/pub/ngircd/>
And as usual: send questions to this list, file bug reports (for bugs and enhancements), send patches, join <irc://irc.barton.de/ngircd>, and have fun! ;-)
Regards
Alex
Hello,
for reasons beyond my understanding, 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.
This took a few days to track down.
So, as a quick hack, the patch attached adds another switch to
getpid.sh. It's already included in the Debian package ngircd-19-1
uploaded a few hours ago.
As briefly discussed in IRC, the whole start-server/getpid thingie is
very fragile and needs a cleanup. Unfortunately, any solution has to
keep in mind ngircd aims to be portable so we cannot use advanced
solutions for the problem of sane daemon starting/stopping like
start-stop-daemon.
Cheers,
Christoph
diff --git a/src/testsuite/getpid.sh b/src/testsuite/getpid.sh
index fd3b342..19ced76 100755
--- a/src/testsuite/getpid.sh
+++ b/src/testsuite/getpid.sh
@@ -13,6 +13,8 @@ elif [ $UNAME = "A/UX" ]; then
PS_FLAGS="-ae"; PS_PIDCOL="1"; HEAD_FLAGS="-1"
elif [ $UNAME = "GNU" ]; then
PS_FLAGS="-ax"; PS_PIDCOL="2"; HEAD_FLAGS="-n 1"
+elif [ $UNAME = "Linux" ]; then
+ PS_FLAGS="ax"; PS_PIDCOL="1"; HEAD_FLAGS="-n 1"
elif [ $UNAME = "SunOS" ]; then
PS_FLAGS="-af"; PS_PIDCOL=2; HEAD_FLAGS="-n 1"
else
