OK, deleted entries and checked:
\# avahi\-daemon
Daemon already running on PID 95
But, it looks like there is a problem (below). Pardon my lack of experience, but where can I find logs on Angstrom?
There are several logs under /var/log/, including /var/log/messages
where many system messages are kept, including ones from the launch of
avahi-daemon.
I found a couple of the hints on
How to debug Systemd problems - Fedora Project Wiki to be
helpful, but be sure to ignore anything about grub.
Just poking around, I did:
root@beaglebone:~# ps auwx | grep syslog
root 60 0.0 0.2 2016 704 ? Ss Apr30 0:04
/lib/systemd/systemd-stdout-syslog-bridge
root 160 0.0 0.6 35892 1592 ? Ssl Apr30 0:08
/usr/sbin/rsyslogd -n -c5
root 7405 0.0 0.2 1776 580 pts/0 S+ 18:04 0:00 grep syslog
From that, I suppose you can configure where syslog messages go with
/etc/rsyslog.conf.
I believe there is a way to get additional log data out of systemd,
but I haven't (re?)found the command line magic, so I could be wrong
on that.
\# systemctl status avahi\-daemon\.service
avahi\-daemon\.service \- Avahi mDNS/DNS\-SD Stack
Loaded: loaded \(/lib/systemd/system/avahi\-daemon\.service; enabled\)
Active: failed \(Result: exit\-code\) since Sun, 02 Jan 2000 00:18:22 \+0000; 12 years and 4 months ago
Main PID: 107 \(code=exited, status=255\)
CGroup: name=systemd:/system/avahi\-daemon\.service
Mine shows:
root@beaglebone:~# systemctl status avahi-daemon.service
avahi-daemon.service - Avahi mDNS/DNS-SD Stack
Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled)
Active: active (running) since Sat, 01 Jan 2000 00:00:05 +0000; 12
years and 4 months ago
Main PID: 104 (avahi-daemon)
Status: "avahi-daemon 0.6.30 starting up."
CGroup: name=systemd:/system/avahi-daemon.service
├ 104 avahi-daemon: running [beaglebone.local]
└ 124 avahi-daemon: chroot helper
Guess there is a chance something is wrong with your config.