On 05/29/2012 08:37 AM, JD wrote:
On 05/29/2012 03:32 AM, Ed Greshko wrote:
On 05/29/2012 03:18 PM, Ed Greshko wrote:
On 05/29/2012 03:11 PM, Ed Greshko wrote:
Third, to work around the problem add the following to the
beginning of the init script.
mkdir /var/run/uuidd
chown uuidd:uuidd /var/run/uuidd
Their seems to be some other minor problems surrounding this
suggestion. Need to
read the script and see what needs to be done for real....but eating
dinner at the
moment.... :-)
What you really want is to add this....
if ! [ -d /var/run/uuidd ]
then
mkdir /var/run/uuidd
chown uuidd:uuidd /var/run/uuidd
fi
That doesn't fix the problem about "systemctl stop uuidd.service" not
stopping the
service.
after adding the lines to create dir /var/run/uuidd
and chowning it; starting the daemon just hangs.
# service uuidd start
Starting uuidd (via systemctl):
And it stays there forever until interrupted.
I spoke too soon.
After about 5 minutes, systemctl reports failure:
# service uuidd start
Starting uuidd (via systemctl): Job failed. See system logs and
'systemctl status' for details. [FAILED]
and in /var/log/messages:
May 29 08:32:23 localhost uuidd[11934]: Starting uuidd: [ OK ]
May 29 08:32:23 localhost systemd[1]: PID file
/var/lib/libuuid/uuidd.pid not readable (yet?) after start.
May 29 08:37:23 localhost systemd[1]: uuidd.service operation timed out.
Terminating.
May 29 08:37:23 localhost systemd[1]: Unit uuidd.service entered failed
state.
# ls -ld /var/lib/libuuid
drwxrwsr-x 2 uuidd uuidd 4096 Apr 17 07:39 /var/lib/libuuid/
So how many pid files does uuidd need?
So far, it seems 2
/run/uuidd/uuidd.pid
and
/var/lib/libuuid/uuidd.pid
At any rate, uuidd stays running:
# ps -C uuidd
PID TTY TIME CMD
11939 ? 00:00:00 uuidd
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
