>BTW, 'nobody' is strictly reserved for NFS use. If any processes run as user 'nobody' then that process would have undue influence over NFS.
Did you miss this bit, where dnsmasq *is* running as "nobody"?
$ sudo ps aux | grep dnsmasq | grep -v grep nobody 3771 0.0 0.0 54552 388 ? S 18:16 0:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper root 3772 0.0 0.0 54524 388 ? S 18:16 0:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
Having two copies of it running doesn't seem like the correct behaviour to me.
>BTW, 'nobody' is strictly reserved for NFS use. If any processes run as user 'nobody' then that process would have undue influence over NFS.
Did you miss this bit, where dnsmasq *is* running as "nobody"?
$ sudo ps aux | grep dnsmasq | grep -v grep file=/var/ lib/libvirt/ dnsmasq/ default. conf --leasefile-ro --dhcp- script= /usr/lib/ libvirt/ libvirt_ leaseshelper file=/var/ lib/libvirt/ dnsmasq/ default. conf --leasefile-ro --dhcp- script= /usr/lib/ libvirt/ libvirt_ leaseshelper
nobody 3771 0.0 0.0 54552 388 ? S 18:16 0:00 /usr/sbin/dnsmasq --conf-
root 3772 0.0 0.0 54524 388 ? S 18:16 0:00 /usr/sbin/dnsmasq --conf-
Having two copies of it running doesn't seem like the correct behaviour to me.