Hello Charles -
On Thu, 20 Jul 2000, Charles Sprickman wrote:
> Hi,
>
> Our adduser script periodically formats (removes certain GIDs/UIDs) then
> copies and chowns master.passwd for radiator. So far, we've had no
> problems with this until today. At exactly the time of file creation,
> radiator started logging all users that are run through AuthBy UNIX as "No
> such user". Sending radiator a HUP cleared this up.
>
> I am assuming I don't have to fire off a HUP everytime the file changes,
> as if I were running radiator as root and working with the real
> master.passwd it could change at any time. Perhaps it's a locking issue?
>
> I've verified the file is not corrupt, and has the same timestamp...
>
There must be a race condition between the modification time on the file
changing and the actual contents of the file being available. I think I might
add a line to your script to "touch" the file after the processing is
completed. This will ensure that the modification time changes after the file
has been written. Alternatively you could write the new file with a different
name, and rename it once processing is finished.
BTW - SQL databases are *much* better for managing user populations.
hth
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc.
Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X.
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
