Is there any sensible way to obtain the process id of radiusd when it is
first started from rc.local and to save that PID to a file, so that
subsequent scripts can kill or restart radiusd as required? (I want to
automate the processing of my daily updates to the users file, and have the
script trigger builddbm, and kill and restart the daemon)
For anything else, I'd use a wrapper to copy $! to a radiusd.pid file
somewhere and consult that, but that won't work for radiusd (as far as I can
determine).
Any suggestions (other than writing a chunk of perl to do a ps ax and grep
for radiusd, and split the output and pull out the PID, which will work but
be a real pain to do). If there were an easier (and more elegant) way, I'd
be happier.
This is radiusd 2.01 running under FreeBSD, btw.
TIA for any pointers,
M.
-- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Mark O'Leary, | Voice: +44 (0161) 2756110 Network Support Officer, | Email: Mark.O'Leary@mcc.ac.uk Manchester Computing, UK | or: mark@mcc.ac.uk - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>