X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=2.9 required=5.0 tests=AWL,BAYES_20,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <49C92CF5.2090509@cat.pdx.edu> Date: Tue, 24 Mar 2009 11:56:53 -0700 From: Darren Pilgrim User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Keeping /etc/{group,passwd} intentionally out of date? Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com 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/