On 10/31/2014 02:30 PM, Matthew Miller wrote:
> Oct 31 09:19:46 ubik systemd[1]: dev-mqueue.mount: Directory /dev/mqueue to 
> mount over is not empty, mounting anyway.
> Oct 31 09:19:46 ubik mount[4484]: mount: mount point /dev/mqueue does not 
> exist
> Oct 31 09:19:46 ubik systemd[1]: dev-mqueue.mount mount process exited, 
> code=exited status=32
> Oct 31 09:19:46 ubik systemd[1]: Failed to mount POSIX Message Queue File 
> System.

I saw this too, but didn't look into it.

> On a related but different note — is there a way to detect potential
> ordering cycles from a set of RPMs on disk (possibly installed in a
> chroot or something) _without_ actually booting? Maybe we could add a
> taskotron check for that for packages with changes to systemd unit
> files. (I realize that what is enabled on people's systems will have an
> impact, but we could check against a set of defaults at least.)

It's not the perfect solution, but this command would report
the cycle you saw:
/usr/lib/systemd/systemd --test --system

Michal
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Reply via email to