This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Keeping /etc/{group,passwd} intentionally out of date?
- From: Darren Pilgrim <pilgrimd at cat dot pdx dot edu>
- To: cygwin at cygwin dot com
- Date: Tue, 24 Mar 2009 11:56:53 -0700
- Subject: Keeping /etc/{group,passwd} intentionally out of date?
We have cygwin installed in a lab with a large number of domain groups
and users. Keeping the /etc/group and /etc/passwd files up to date is
impractical due to the rate of account turn-over. Cygwin Bash Shell has
been giving us the error messages produced from /etc/profile nagging us
to run mkgroup and mkpasswd.
Is there anything that will for sure break if our domain user/group
information isn't kept current in those files? Same question but for
local group/user information? Is the effect like that in other unix
environments--cosmetic and you're limited to specifying numeric IDs? I
can't find anything obvious and non-cosmetic that would break if these
files didn't contain the user's information. Can I just rip out the
checks and be done with it?
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/