Denis Antrushin wrote:
Apparently, supplying -d EXITING_HOME_DIR stops -s from setting the
shell.
Well, it cause some other option to work as well. :-)
Oops, I meant to say "it causes some other options to stop working as well"
___
[EMAIL PROTECTED] mail
Richard Caley wrote:
I thin this exists in both -STABLE and -CURRENT, but I don't have a
bang up to date instalation of either, so appologies if it has been
fixed.
No, it still present in current version (pw_user.c, as of ver. 1.55)
Tested on 5.2.1 and 4.8. may have some security implications in th
I thin this exists in both -STABLE and -CURRENT, but I don't have a
bang up to date instalation of either, so appologies if it has been
fixed.
Tested on 5.2.1 and 4.8. may have some security implications in that
someone may think they have changed a shell (eg to /nonexistant) but
they haven't rea
On Sun, Jun 23, 2002 at 09:00:52AM -0700 I heard the voice of
Paul Herman, and lo! it spake thus:
> On Sun, 23 Jun 2002, Geoffrey C. Speicher wrote:
>
> How so? I'm not suggesting unlink(2)ing /etc/master.passwd or
> /etc/spwd.db at all.
No, but pw(8) does; making it not do so would require rea
On Sun, 23 Jun 2002, Geoffrey C. Speicher wrote:
> > Keep it simple. Do what you mean. If you want to make changes to
> > /etc/master.passwd then open(2) /etc/master.passwd with O_EXLOCK.
>
> As Matt Fuller already pointed out in a follow-up, that brings us back to
> where we were when we start
Sorry for the slooow response, I've had problems you wouldn't believe
with my email...
On Fri, May 17, 2002 at 06:40:57PM -0400 I heard the voice of
Geoffrey C. Speicher, and lo! it spake thus:
>
> 1. The lock isn't very fine-grained. We grab one giant lock before
> doing any operation
