On Mon, Feb 06, 2006 at 06:40:55PM -0800, Steve Langasek wrote: > On Mon, Feb 06, 2006 at 06:17:03PM -0800, Ivan Kohler wrote: >> Package: freeradius >> Version: 1.1.0-1 >> Severity: normal
>> "/etc/init.d/freeradius restart" doesn't start freeradius if it isn't already >> running. "$0 stop" returns an unsucessful exit status and the script stops. >> [EMAIL PROTECTED]:~# /etc/init.d/freeradius restart >> Stopping FreeRADIUS daemon: freeradius# >> [EMAIL PROTECTED]:~# >> Policy 9.3.2 says that "restart" should start the service if it isn't already >> running. >> This also causes package configuration to fail if you're installing a new >> freeradius-mysql package and the old daemon isn't running: > True, but that suggests "restart" is the wrong argument to be using here, > doesn't it? Since installation of freeradius-mysql shouldn't cause the > daemon to be started if it wasn't already running. This was chosen over the more traditional "stop in prerm, start in postinst" as RADIUS is an authentication server and having it down while files are copied around seemed too risky. Especially if this server authenticates the Internet link you're connected to the server by. -_- Perhaps I'll add a 'restart-if-running' for use by postinst scripts... Ideally, it shouldn't be doing the 'restart' until the end of the upgrade run, or you'll restart a running RADIUS into one that is running but without mySQL support, and then restart it again when freeradius-mysql gets processed (for example). Which is a problem I recall a few packages hitting (SELinux policies?) and don't recall a solution for. -- Paul "TBBle" Hampson, [EMAIL PROTECTED] Shorter .sig for a more eco-friendly paperless office.
pgpEeFX6mMG9d.pgp
Description: PGP signature
