View Issue Details

IDProjectCategoryView StatusLast Update
0002956unrealircdpublic2006-06-07 06:33
Reporterkayelem Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionwont fix 
Product Version3.2.4 
Summary0002956: /restart on chrooted ircd fails
DescriptionAttempting /restart with ircd chrooted with CHROOTDIR, IRC_UID and IRC_GID defined fails. Server dies but does not restart.

Suspect it may be attempting to re-chroot itself, finds it can't, then exits?

For now I've commented out "can_restart" from my oper block.
3rd party modules

Activities

syzop

2006-06-07 06:10

administrator   ~0011912

I guess.
Then again, how could the new instance of the IRCd know it was already chrooted? Surely it can't be a good reason to just ignore the chdir() error? Plus it will get a chroot() error indeed, especially if it's running with non-root uid.
Difficult.. :P

Restarting the IRCd chrooted is fun anyway, eg: you might also need a <unrealdir>/etc/resolv.conf, and unless I'm crazy you'll need all the libraries unreal uses (libc etc) as well in <unrealdir>/lib, etc...

I guess, in short, not exactly recommended, nor easy, to restart a chrooted ircd on the command line :p.

PS: I do run chrooted myself, but.. I never /restart ;p

kayelem

2006-06-07 06:24

reporter   ~0011913

Fair enough. Given on the rare occasions I might need to restart, I can do it from a shell on the server this is minor anyway.

At least it's covered now, in case anyone else trips over this. Feel free to set it to "won't fix"

syzop

2006-06-07 06:27

administrator   ~0011914

Last edited: 2006-06-07 06:27

*nod*
and it should be documented somewhere, and block /RESTART all together if chrooted since currently all it does is act like a /DIE :P.

EDIT: -maybe

syzop

2006-06-07 06:32

administrator   ~0011915

And done so in CVS (the disable thing).

syzop

2006-06-07 06:33

administrator   ~0011916

Thanks for the report though :P. Perhaps it will save someone from accidently killing his ircd in a particulary nasty situation.

Issue History

Date Modified Username Field Change
2006-06-07 04:04 kayelem New Issue
2006-06-07 06:10 syzop Note Added: 0011912
2006-06-07 06:24 kayelem Note Added: 0011913
2006-06-07 06:27 syzop Note Added: 0011914
2006-06-07 06:27 syzop Note Edited: 0011914
2006-06-07 06:32 syzop Note Added: 0011915
2006-06-07 06:33 syzop Status new => closed
2006-06-07 06:33 syzop Note Added: 0011916
2006-06-07 06:33 syzop Resolution open => wont fix