This is the mail archive of the cygwin-patches@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: [PATCH]: Check modification time on /etc/passwd and /etc/group


Corinna Vinschen wrote:
> 
> On Mon, Aug 06, 2001 at 07:57:04AM -0600, Earnie Boyd wrote:
> > Corinna Vinschen wrote:
> > >
> > > On Sun, Aug 05, 2001 at 12:29:54PM -0400, Christopher Faylor wrote:
> > > > So, is it worthwhile to make this change?  We might be adding some overhead
> > > > for an infrequent case.
> > >
> > > Hmm, that's a good question. I would like to see that handled
> > > correctly w/o having to stop and start my services again. And
> > > it's actually no infrequent case for sysadmins to add users.
> > >
> >
> > Robert Collins had some interesting questions on this subject in this
> > http://www.cygwin.com/ml/cygwin-developers/2001-04/msg00071.html post.
> >
> > And http://www.sxlist.com/techref/os/win/api/win32/func/src/f24_9.htm is
> > Win32 API documentation for FindFirstChangeNotification.
> 
> Yep, I know that function but I wasn't too keen to start
> another thread per process just to get a notification.
> 

Couldn't the initialization routines map the files to memory and issue
the notification, listen for the event, block reads to /etc/passwd and
/etc/group, remap the file to memory, unblock and reissue the
notification?

Forgive my ignorance in this, I'm just learning and conceptualizing.

Earnie.

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]