Hello Alan, today I upgraded from freeradius-2.1.1 to 2.1.3 and stumbled because freeradius does not erase the socket file in /var/run/radiusd. -- Mit freundlichen Grüßen Hans-Peter Fuchs Hans-Peter Fuchs - RRZK Zimmer 20 Zentrum für angewandte Informatik - Universitätsweiter Service RRZK Universität zu Köln - Tel: 0221-470-6972
Hans-Peter Fuchs wrote:
today I upgraded from freeradius-2.1.1 to 2.1.3 and stumbled because freeradius does not erase the socket file in /var/run/radiusd.
What kind of "stumble"? The socket file isn't erased automatically when the server exits. If something *forces* the server to exit quickly, then the socket file cannot be deleted by the server. So there are cases where it will always be around after the server exits. Alan DeKok.
Hello Alan, freeradius-2.1.1 created the socket with 'radiusd' as owner and freeradius-2.1.3 throw error: Error: We do not own /var/run/radiusd/radius1.sock because it created it with owner root. Am Donnerstag, den 29.01.2009, 14:19 +0100 schrieb Alan DeKok:
Hans-Peter Fuchs wrote:
today I upgraded from freeradius-2.1.1 to 2.1.3 and stumbled because freeradius does not erase the socket file in /var/run/radiusd.
What kind of "stumble"?
The socket file isn't erased automatically when the server exits. If something *forces* the server to exit quickly, then the socket file cannot be deleted by the server.
So there are cases where it will always be around after the server exits.
Alan DeKok. -- Mit freundlichen Grüßen
Hans-Peter Fuchs Hans-Peter Fuchs - RRZK Zimmer 20 Zentrum für angewandte Informatik - Universitätsweiter Service RRZK Universität zu Köln - Tel: 0221-470-6972
Hans-Peter Fuchs wrote:
Hello Alan,
freeradius-2.1.1 created the socket with 'radiusd' as owner and freeradius-2.1.3 throw error: Error: We do not own /var/run/radiusd/radius1.sock because it created it with owner root.
This is a bug in 2.1.3 that will be fixed in 2.1.4. Alan DeKok.
participants (2)
-
Alan DeKok -
Hans-Peter Fuchs