Hi Alexander,
I feel stupid, I admin I did not read the documentation. I expected it was meant for Idle client connections and that it shutdowns the client connections which are idle. Thanks for pointing this out to me, a classic RTFM would helped me ;)
Regards,
Michiel
Op Mar 30, 2014 om 6:36 AM heeft Alexander Barton alex@barton.de het volgende geschreven:
Hi Michiel!
Am 2014-03-29 18:20, schrieb Michiel van Es:
I think I fixed it by commenting one of the following options: ;ConnectRetry = 60 ;IdleTimeout = 60 ;PingTimeout = 120 ;PongTimeout = 20 ;RequireAuthPing = yes At least connections are now stable and Ngircd does not shutdown itself anymore. Do you know which option could have caused the automatic shutdown of Ngircd?
Did you check the description of these options? ;-)
From ./doc/sample-ngircd.conf:
# Number of seconds after which the whole daemon should shutdown when # no connections are left active after handling at least one client # (0: never, which is the default). # This can be useful for testing or when ngIRCd is started using # "socket activation" with systemd(8), for example. ;IdleTimeout = 0
And you used "IdleTimeout=60" -- so ngIRCd exited itself when the last Connection has been terminated (for whatever reason) and no new connection came in within 60 seconds.
So the behaviour you reported is expected. Because you configured it to behave like this ;-)
Regards Alex
ngIRCd Mailing List: ngIRCd-ML@arthur.barton.de http://arthur.barton.de/mailman/listinfo/ngircd-ml