(RADIATOR) BUG? pidfile is written to early

[Mike McCauley]

Hi Charly,

thanks for your suggestion.
There is now a new patch for radius that writes the PidFile much later in the 
startup process, after the Radius ports are created.

Cheers.

On Monday 24 January 2005 19:34, Karl Gaissmaier wrote:
> Hi Mike or Hugh,
>
> maybe due to some different problems, a second radius daemon
> gets started even if one is already running then the content of
> the pidfile is wrong (shows the pid of the died second radiusd)
>
> The second startup normally fails with a bind error:
> (address already in use)
> but the second radiusd writes the pid file to early, even when
> the second daemon can't get the socket.
>
> Additional startup/restart scripts, depending on the proper
> pidfile content, will fail.
>
> Best regards
> 	Charly

-- 
Mike McCauley                               mikem at open.com.au
Open System Consultants Pty. Ltd            Unix, Perl, Motif, C++, WWW
9 Bulbul Place Currumbin Waters QLD 4223 Australia   http://www.open.com.au
Phone +61 7 5598-7474                       Fax   +61 7 5598-7070

Radiator: the most portable, flexible and configurable RADIUS server 
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, 
Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS, 
TTLS, PEAP etc on Unix, Windows, MacOS etc.

--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.