There is a multi step build/backup procedure that only one person should be running at a time. The idea was to restrict the build scripts to only one user. Then allow the build UID only one login at a time.
A "lock" file may be left locked and need to be reset if someone does not complete the procedure.
Maybe a real make file is needed, but it would be complicated.
Does anyone have a better idea?
From: Adam Thornton <[EMAIL PROTECTED]> Reply-To: Linux on 390 Port <[email protected]> To: [email protected] Subject: Re: Restrict user to only one active login Date: Wed, 18 May 2005 15:15:43 -0500
On May 18, 2005, at 3:05 PM, John Campbell wrote:
It would strike me that this would be almost trivial to sneak into the pam.d stack...
...except that I seem to recall that SSH doesn't pay much attention to that.
I would suggest getting the source to OpenSSH's sshd daemon and figuring out how to sneak in such a feature and implementing it locally... and then see if anyone else wants the patch.
(Imagines how many people would put up their hand saying "Me! Me!")
What's the benefit of implementing this? Why do you want to restrict a user to one login at a time?
Adam
---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
