(RADIATOR) BUG? pidfile is written to early

[Karl Gaissmaier]

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
-- 
Bitte unterstuetzt die Softwarepatentgegner:
http://www.nosoftwarepatents.com/de/m/intro/index.html

Karl Gaissmaier       KIZ/Infrastructure, University of Ulm, Germany
Email:karl.gaissmaier at kiz.uni-ulm.de           Service Group Network
Tel.: ++49 731 50-22499
ca-cert: https://imap.uni-ulm.de/certs/KIZ-CA.crt
my-cert: https://imap.uni-ulm.de/certs/26.pem

--
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.