Hi,
I am here on v20 of systemd and wanted to setup a local
fetchmail/postfix solution by following the hints in [1].
As my system changes daily (I am on linux-next), it took some time to
understand what piece of software is doing the harm.
After deinstallation of postfix, my system starts again
Heya,
Just wanted to mention that systemd git now logs its own messages with
facility=LOG_DAEMON to kmsg, and messages from processes it spawns with
LOG_USER. It will no longer strip the facilities passed in from daemons.
The net effect should be that all log messages routed through systemd to
Hey,
the underlying problem described below, is in no way specific to
systemd, it applies to all modern systems and services, existing ones,
or ones not even developed.
The udev systemd service files for udev do no longer pull-in the
barrier 'udevadm settle'. The udev coldplug run is executed
There is, of course, one use for settle; I like to have a monitor
running during boot that creates /var/log/udev - settle is as good a
command as any to kill monitor when it's done.
On Thu, Mar 31, 2011 at 11:35 AM, Kay Sievers kay.siev...@vrfy.org wrote:
Hey,
the underlying problem described
Heya,
A few minutes ago there was a discussion on #systemd involving lots of
folks (from various distros even), regarding the chaotic setup of
/var/lock on most distros. As it turns out every distro set this up
differently, and almost all of them insecurely in one way or another.
I'd like to see
