On 05/28/2012 11:04 PM, JD wrote:
Booting with every fc16 kernel, I always get this failure.
Boot.log shows
Failed to start LSB: UUID daemon FAILED
See 'systemctl status uuidd.service' for details.
# systemctl status uuidd.service
uuidd.service - LSB: UUID daemon
Loaded
On 05/29/2012 11:12 AM, Thibault Nélis wrote:
rpm -q --whatrequires uuidd
Yes I know that, but in the past, when I
wanted to build from source non-fedora distro apps,
some of them would require it.
For the time being, I will disable it.
--
users mailing list
users@lists.fedoraproject.org
To uns
On 05/29/2012 06:21 PM, JD wrote:
I am not running anything that I KNOW to require uuidd.
I simply wanted to make sure that if there are other daemons
or apps that need it, will be able to use it.
You could try
$ rpm -q --whatrequires uuidd
--
t
--
users mailing list
users@lists.fedora
On 05/29/2012 08:39 AM, Ed Greshko wrote:
On 05/29/2012 11:37 PM, JD wrote:
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.
Yes, I know. I me
On 05/29/2012 08:37 AM, Ed Greshko wrote:
On 05/29/2012 10:51 PM, JD wrote:
Will file a bug if one has not been files already.
But if it is broken in f16 and f17, seems
unlikely the devs do not know about it.
I think you meant "likely the devs do not know about it".
Let us know the bug ID afte
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
On 05/29/2012 11:37 PM, JD wrote:
> 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.
Yes, I know. I mentioned that in another message. Y
On 05/29/2012 10:51 PM, JD wrote:
> Will file a bug if one has not been files already.
> But if it is broken in f16 and f17, seems
> unlikely the devs do not know about it.
I think you meant "likely the devs do not know about it".
Let us know the bug ID after filing. Also, I am curious, what pi
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
On 05/29/2012 03:32 AM, Ed Greshko wrote:
if ! [ -d /var/run/uuidd ]
then
mkdir /var/run/uuidd
chown uuidd:uuidd /var/run/uuidd
fi
Thanx Ed.
Will file a bug if one has not been files already.
But if it is broken in f16 and f17, seems
unlikely the devs do not know about it.
--
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 surround
On 05/29/2012 03:11 PM, Ed Greshko wrote:
> First, file a bugzilla.
I've decided not to spend any more time on this as uuidd appears to be broken
in more
than one way. It is also broken in more than one way +1 in F17.
First, if you install uuidd the /var/run/uuidd directory is created and you c
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
On 05/29/2012 02:04 PM, JD wrote:
> Booting with every fc16 kernel, I always get this failure.
> Boot.log shows
> Failed to start LSB: UUID daemon FAILED
> See 'systemctl status uuidd.service' for details.
> # systemctl status uuidd.service
> uuidd.service - LSB: UUID daemon
>
14 matches
Mail list logo
