Bug#408665:

On Wed, 21, Mar, 2007 at 03:31:35PM +0100, Bluefuture spoke thus.. > Hi, > I think that this bugs is to be set from normal to important priority. > For example could be a big issue for production system like ISP, that > accounting data will be falsified by a shutdown or a reboot of the > machine.

Bug#408665:

Hi, I think that this bugs is to be set from normal to important priority. For example could be a big issue for production system like ISP, that accounting data will be falsified by a shutdown or a reboot of the machine. Regards, Ste -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subj

Bug#408665: freeradius init order

This one time, at band camp, Mihai said: > debian etch init order (runlevels) > freeradius is closed _after_ mysql in runlevel 0 and 6. If we have radius > users stored in > mysql, when machine goes down (runlevel 0 or 6) freeradius cannot close > sessions because mysql is > already closed. > >

Bug#408665: freeradius init order

Package: freeradius Version: 1.1.3-3 debian etch init order (runlevels) freeradius is closed _after_ mysql in runlevel 0 and 6. If we have radius users stored in mysql, when machine goes down (runlevel 0 or 6) freeradius cannot close sessions because mysql is already closed. mumu:~# ls -l /etc