[systemd-devel] systemd --test still tries to execute quite some actions and fails

Andrey Borzenkov arvidjaar at gmail.com
Sat Feb 19 03:23:57 PST 2011


On Fri, Feb 18, 2011 at 2:44 PM, Lennart Poettering
<lennart at poettering.net> wrote:
> On Fri, 18.02.11 14:38, Andrey Borzenkov (arvidjaar at gmail.com) wrote:
>
>> >> Failed to allocate manager object: No such file or directory
>> >
>> > The only real problem here is the last line, the rest is ignored.
>>
>> No. The real problem is that it tries to do all of this. Fortunately
>> it is not permitted if running as non-root.
>
> Yupp, and we rely on that.
>

Then it should refuse to run as root, should not it?

>> Failed to allocate manager object: No such file or directory
>> [bor at n2 ~]$
>
> Hmm, my guess is that this has something to do with the lacking autofs4
> support. Unfortunately the log messages don't give us a hint what is
> going on. May I ask you to gdb through manager_new and check which of
> the operations it does actually fails?
>

Well, it runs on my own system, and system where it failed is rather
tightly controlled were I have only limited access (and second case
was chroot with even more restricted environment). I am not sure I
will be able to do any investigation in near future, unfortunately.


More information about the systemd-devel mailing list