0003566: Make bind errors non-fatal - UnrealIRCd Bug Tracker

ID	Project	Category	View Status	Date Submitted	Last Update
0003566	unreal	ircd	public	2008-01-04 19:31	2016-01-11 18:14

Reporter	Stealth	Assigned To	syzop
Priority	normal	Severity	tweak	Reproducibility	always
Status	closed	Resolution	no change required
Product Version	3.2.7

Summary	0003566: Make bind errors non-fatal
Description	A feature I like that Insp has is when the IRCd boots bind errors are only fatal if the IRCd fails to open all the ports. In the event some ports are not opened, Insp outputs which ports were not opened, and continues to boot as normal. Example in Additional Info
Additional Information	WARNING: Not all your client ports could be bound --. Starting anyway with 9 of 11 client ports bound.. The following port(s) failed to bind:. 1. IP: 1.2.3.4 Port: 6667. 2. IP: 1.2.3.4 Port: 6668.

3rd party modules

syzop 2013-01-09 10:57 administrator ~0017337	I'd like feedback from others on this. Whatever we decide, if everything fails and we don't listen on any port, we must exit. My opinion: in all cases I encountered this I felt there was an urgent need to fix the config, so then fatal on any bind error is the way to go. But as said, I'd like to hear others on this.

~~nenolod~~ 2013-01-14 10:48 reporter ~0017362	I agree with Syzop here, bind errors should remain fatal.

syzop 2016-01-11 18:14 administrator ~0019039	In UnrealIRCd 4 we output nicely on which ports the IRCd is listening. Any bind errors are fatal, since these may indicate a serious problem that needs to be corrected.

Date Modified	Username	Field	Change
2008-01-04 19:31	Stealth	New Issue
2013-01-09 10:57	syzop	Note Added: 0017337
2013-01-09 10:57	syzop	Status	new => feedback
2013-01-14 10:48	~~nenolod~~	Note Added: 0017362
2016-01-11 18:14	syzop	Note Added: 0019039
2016-01-11 18:14	syzop	Status	feedback => closed
2016-01-11 18:14	syzop	Assigned To	=> syzop
2016-01-11 18:14	syzop	Resolution	open => no change required