Hi, I use FRadius accounting. OpenSer tries to use a file /var/run/radius.seq but it fails when restarting computer since OpenSer init script creates this file as: /var/run/openser/openser_radius.seq
create_radius_seqfile () { # Create a radius sequence file to be used by the radius client if # radius accounting is enabled. This is needed to avoid any issue # with the file not being writable if openser first starts as user # root because DUMP_CORE is enabled and creates this file as user # root and then later it switches back to user openser and cannot # write to the file. If the file exists before openser starts, it # won't change it's ownership and will be writable for both root # and openser, no matter what options are chosen at install time RADIUS_SEQ_FILE=/var/run/openser/openser_radius.seq
I don't find where to change this file in OpenSer script. Isn't a bug if default value is: /var/run/radius.seq but OpenSer init script (Debian Etch) creates it in: /var/run/openser/openser_radius.seq ?
El Tuesday 27 May 2008 11:58:34 Iñaki Baz Castillo escribió:
I don't find where to change this file in OpenSer script. Isn't a bug if default value is: /var/run/radius.seq but OpenSer init script (Debian Etch) creates it in: /var/run/openser/openser_radius.seq ?
Ok, this is configured in radius client, not related to OpenSer:
/etc/radiusclient-ng/radiusclient.conf ------------- # file which holds sequence number for communication with the # RADIUS server seqfile /var/run/radius.seq -------------
But I'll report the bug since init script creates /var/run/openser/openser_radius.seq while default file in modules/acc/etc/radiusclient.conf points to /var/run/radius.seq.