I'm really not sure about actual comments, though I lean towards it's a bad thing because the people who write the progs usually leave a few in there for you.
Safer is to put a department code into the GECOS field, then write a script that will group by dept. or pick out particular depts. you can even put a little wrapper round useradd to do that. rick On Mon, 05 Mar 2001, Christopher W. Aiken wrote: > What I was trying to do is arange my passwd file by > departments, like this: > > > ############## accounting dept ############### > user1:x:............. > user2:x:.............. > user3:x:....... > ############## Developmet dept ################ > user1:x:............. > user2:x:.............. > user3:x:....... > ############## Research dept ################ > user1:x:............. > user2:x:.............. > user3:x:....... > > > -=[cwa]=- > > On Mon, 5 Mar 2001, Wes Wannemacher wrote: > > :)On Mon, Mar 05, 2001 at 01:58:28PM -0500, Christopher W. Aiken wrote: > :)> > :)> A general question (i.e. not Debian specific) about > :)> the /etc/passwd file. Can "comment" lines (i.e "#") > :)> or "blank" lines be inserted into the /etc/passwd file > :)> w/o causing havoc on a Linux system? > :)> > :) > :)Blank lines are a definite no-no. There is a comment section of the > :)standard entry. Is this space insufficient? If you need more > :)functionality, you may need to take a look at LDAP. Even though it > :)doesn't work well with Debian. > :)Here at the University we store all user account information in a MySQL > :)database. We run scripts frequently to update our debian systems with > :)the appropriate data from the database. If you implement a solution like > :)this, you can add / change the MySQL any way you want, just make sure > :)that your scripts only update the /etc/passwd file appropriately. > :) > :)->W > :) > :) > > -- > Christopher W. Aiken, Scenery Hill, Pa, USA > chris at cwaiken dot com, www.cwaiken.com > : > A bus station is where a bus stops. > A train station is where a train stops. > On my desk, I have a work station........ > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] >