5rc-16c: Failed to find user 'avahi'

[graywolf]

I know that avahi is for Mac stuff which I do not have and figure it can be ignored but did find this thread:

 

http://lime-technology.com/forum/index.php?topic=9902.msg132716#msg132716

 

My /boot/config/passwd is:

root:$1$nN81VOjR$K.5opzoWhtFB3ceWNCRQa.:0:0::/root:/bin/bash
bin::1:1:bin:/bin:/bin/false
daemon::2:2:daemon:/sbin:/bin/false
adm::3:4:adm:/var/log:/bin/false
lp::4:7:lp:/var/spool/lpd:/bin/false
sync::5:0:sync:/sbin:/bin/sync
shutdown::6:0:shutdown:/sbin:/sbin/shutdown
halt::7:0:halt:/sbin:/sbin/halt
mail::8:12:mail:/:/bin/false
news::9:13:news:/usr/lib/news:/bin/false
uucp::10:14:uucp:/var/spool/uucppublic:/bin/false
operator::11:0:operator:/root:/bin/bash
games::12:100:games:/usr/games:/bin/false
ftp::14:50::/home/ftp:/bin/false
smmsp::25:25:smmsp:/var/spool/clientmqueue:/bin/false
mysql::27:27:MySQL:/var/lib/mysql:/bin/bash
rpc::32:32:RPC portmap user:/:/bin/false
sshd::33:33:sshd:/:/bin/false
gdm::42:42:GDM:/var/state/gdm:/bin/bash
apache::80:80:User for Apache:/srv/httpd:/bin/false
messagebus::81:81:User for D-BUS:/var/run/dbus:/bin/false
haldaemon::82:82:User for HAL:/var/run/hald:/bin/false
pop::90:90:POP:/:/bin/false
nobody::99:99:nobody:/:/bin/false
user1:x:1000:100:user1:/:/bin/false
user2:x:1001:100:user2:/:/bin/false
user3:x:1002:100:user3:/:/bin/false
user4:x:1003:100:user4:/:/bin/false
user5:x:1004:100:user5:/:/bin/false
user6:x:1005:100:user6:/:/bin/false

 

Should I just add the following to /boot/config/passwd?

avahi:x:61:214:Avahi Daemon User:/dev/null:/bin/false
avahi-autoipd:x:62:62:Avahi AutoIP Daemon User:/dev/null:/bin/false

 

Just went from 5b11 to 5rc16c

 

 

[dgaschk]

Why it's missing is the question. Did you delete the following when upgrading from 4.7:

 

config/passwd

config/shadow

config/smbpasswd

 

Delete them now. You will have to reenter your users.

[graywolf]

Did not upgrade from 4.7 but rather from 5b11

 

Followed these steps as documented.

     Prepare the flash: either shutdown your server and plug the flash into your PC or Stop the array and perform the following actions referencing the flash share on your network:
        Copy the files bzimage and bzroot from the zip file to the root of your flash device, overwriting the same-named files already there. 
    Reboot your server. Once boot-up has completed, you should see "Stopped. Configuration valid." array status with all disks assigned correctly.
    Click on each disk link on the Main page and examine the Partition format field. If you see "MBR: error", or "MBR: unknown" for any disk, do not Start the array; instead post your finding in the Forum announcement thread for this release. If everything looks ok, click Start to bring the array on-line.
    Go to Utils/New Permissions and execute that utility to change file ownership and permission settings. This is necessary for proper operation of the 5.0 security model. 

 

Nothing said anything about deleting those files.

 

BTW, added those 2 users to the /boot/config/passwd file and no longer get the errors about avahi not found, nor the associated avahi-daemon errors.

 

 

[graywolf]

By doing this, it reduced/eliminated the "hang" when restarting smb/avahi since avahi was not timing/erroring out