Re: systemctl daemon-reload causes message "Failed to connect to bus: No such file or directory"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 02/27/2017 11:49 AM, Martin Gansser wrote:
On 02/27/2017 10:32 AM, Martin Gansser wrote:

This is an upstream makefile bug.  Preparing an installation tree should
not attempt to reload or restart system daemons.  In a mock chroot, this
does not work because typically, systemd is not running inside the chroot.

Florian

The developer told me the following: ( https://projects.vdr-developer.org/issues/2476#note-3 )
If you are in normal environment, you get without a reload after systemd always messages that a reload still pending.
Is there a flag, for example, 'DO_NOT_RELOAD_INIT_SYSTEM', which is given for the build in an installation tree? Or how do you recognize that you are in an installation tree? Primarily, the "make install" is designed for live environments.

A set DESTDIR variable should be a good approximation to that.

Florian
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux