> /etc/init.d/freeradius reload
> - either is seems broken, or freeradius misinterprets the SIGHUP with > exiting instead relaoding config (?) don't know where the problem > exactly is
I noticed this recently, but haven't had a chance to backtrace it... Definately put that one in bugs.freeradius.org. Unknown to me if it is Debian-specific. I'm assuming it is since no-one's reported it to bugs.freeradius.org, and there's bugreports there from things that _do_ break during SIGHUP. :-)
I tried to track this a bit further; when I send a SIGHUP with
kill -s SIGHUP <pid> freeradius dies without any notice, so it looks more like a debian-independent problem, but I'm too far
from any detail to confirm this being a bug..
I'll go file a bugreport now...
Bugreport #63. It's 1.0.0 release blocker too.
Delete the line, and remove the build-dependancy on the versioned debhelper. That's the only thing that won't work with Woody's debhelper. If you want the pam file, drop --name=radiusd, but you'll have to edit the pam configuration in FreeRADIUS to use it under whatever name it gets.
ok, thats what I already did the last 5 times.
I don't need PAM, so I don't care.. just thought because, one year (and
knowledge) ago such things would've probably left me out from using
freeradius on woody ;)
I've recently gotten pbuilder-uml working at home, and so will be
able to test the build under Debian/Woody. Someone else (in fact a
few people) are also doing Woody backports. I don't know if they're
tracking CVS though.
--
Paul "TBBle" Hampson, on a webmail client!
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
