In the book, we create a lot of users and groups. Almost none of them have uids/gids specified. Right now, if a user/group is created without specifying, a uid value > 1000 or a gid value > 100 is used. The LSB says system uids/gids should be below 100. I am proposing a book wide coordinated set of numbers:
Users apache 25 bin 1 bin 1 lp 9 courier 30 named 20 exim 31 gdm 21 fcron 22 fcron 22 ftp 45 apache 25 gdm 21 courier 30 games 60 exim 31 lp 9 postfix 32 mysql 40 sendmail 34 named 20 vmailman 35 news 36 news 36 nobody 99 nfsnobody 65534 mysql 40 postfix 32 postgres 41 postgres 41 ftp 45 proftpd 46 proftpd 46 rsyncd 48 vsftpd 47 sendmail 34 rsyncd 48 sshd 50 sshd 50 stunnel 51 stunnel 51 svn 56 svn 56 vmailman 35 games 60 vsftpd 47 nobody 99 nfsnobody 65534 Groups apache 25 usb 14 courier 30 named 20 exim 31 gdm 21 fcron 22 fcron 22 ftp 45 apache 25 games 60 smmsp 26 gdm 21 courier 30 mail 34 exim 31 mysql 40 postfix 32 named 20 postdrop 33 news 36 mail 34 postdrop 33 vmailman 35 postfix 32 news 36 proftpd 46 mysql 40 rsyncd 48 ftp 45 smmsp 26 proftpd 46 sshd 50 vsftpd 47 stunnel 51 rsyncd 48 svn 56 sshd 50 svntest 57 stunnel 51 usb 14 svn 56 vmailman 35 svntest 57 vsftpd 47 games 60 nogroup 99 nogroup 99 nfsnogroup 65534 nfsnogroup 65534 The first column is sorted alphabetically and the second numerically. I tried to keep somewhat similar functions close together. Note, the issue of nobody is only relevant on nfs servers and I will explain in the nfs-utils section the reasons to use (or not) nfsnobody/group. That is, if exportfs specifies annonuid and annongid, the -2 values are never used. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
