| Age | Commit message (Collapse) | Author |
|---|
|
Various operations done by systemd-tmpfiles may only be safely done at
boot (e.g. removal of X lockfiles in /tmp, creation of /run/nologin).
Other operations may be done at any point in time (e.g. setting the
ownership on /{run,var}/log/journal). This distinction is largely
orthogonal to the type of operation.
A new switch --unsafe is added, and operations which should only be
executed during bootup are marked with an exclamation mark in the
configuration files. systemd-tmpfiles.service is modified to use this
switch, and guards are added so it is hard to re-start it by mistake.
If we install a new version of systemd, we actually want to enforce
some changes to tmpfiles configuration immediately. This should now be
possible to do safely, so distribution packages can be modified to
execute the "safe" subset at package installation time.
/run/nologin creation is split out into a separate service, to make it
easy to override.
https://bugzilla.redhat.com/show_bug.cgi?id=1043212
https://bugzilla.redhat.com/show_bug.cgi?id=1045849
|
|
Condition for /lib (necessary for split /usr) was missing from the unit.
Some changes which were done in tmpfiles.d(5) were not carried over to
systemd-tmpfiles(1).
Also use markup where possible.
|
|
systemd-delta /run/systemd/system will show all unit overrides
in /run, etc.
|
|
Also, introduce a new environment variable named $WATCHDOG_PID which
cotnains the PID of the process that is supposed to send the keep-alive
events. This is similar how $LISTEN_FDS and $LISTEN_PID work together,
and protects against confusing processes further down the process tree
due to inherited environment.
|
|
commit 5b04fe60004e7c5cd5a43648ede3e6a965e70b8c broke it with
‘./man/sd_session_is_remote.3’: No such file or directory
|
|
|
|
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732798
|
|
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732798
|
|
|
|
|
|
In journalctl(1), be more explicit about the reference to "Seal=" in
journald.conf(5) and what information can be found there.
|
|
journalctl(1)
It may not be immediately obvious to the reader what "ID128" is, so replace the
example option argument "ID128" with "128-bit-ID".
|
|
And add a missing <option> tag around "--setup-keys" under "--force".
|
|
Also clean things up a bit here and there.
|
|
|
|
|
|
|
|
|
|
These specifiers require NSS lookups to work, and we really shouldn't do
them from PID 1 hence. With this change they are now only supported for
user systemd instance, or when the configured user for a unit is root.
|
|
So far the compatibility with .desktop settings hasn't been imporant
at all, and we do not want people to write convoluted unit
files.
|
|
We have lots of questions from people who assume that shell syntax works
here, so let's be very explicit what is allowed and what is not. A few
examples should also help.
http://bugs.debian.org/732156
|
|
gettys on ptys
|
|
container to spawn
|
|
|
|
Taken from https://bugs.freedesktop.org/show_bug.cgi?id=68369.
|
|
|
|
Also split into paragraphs for easier reading and make a few minor
corrections.
|
|
This adds the new library call sd_journal_open_container() and a new
"-M" switch to journalctl. Particular care is taken that journalctl's
"-b" switch resolves to the current boot ID of the container, not the
host.
|
|
udev rules
https://bugzilla.redhat.com/show_bug.cgi?id=1026860
|
|
Improve wording under "Description" and "_KERNEL_DEVICE="
|
|
https://bugzilla.redhat.com/show_bug.cgi?id=953077
|
|
Use [brackets] only for optional elements.
Use <optional> in XML sources.
|
|
It is nicer to say 'systemctl list-units ssh\*' then to use grep,
because colouring is preserved and it is easier to match just against
the unit name.
|
|
The option 'M' is inconsistent between help document and man page.
|
|
other calls
Instead of returning an enum of return codes, make them return error
codes like kdbus does internally.
Also, document this behaviour so that clients can stick to it.
(Also rework bus-control.c to always have to functions for dbus1 vs.
kernel implementation of the various calls.)
|
|
Those files can be in a completely deferent format and also
arbitrarily long, and usually contain information about other
stuff. If we ever add SourceLine= or SourceLines= in addition
to SourcePath=, and can show the relevant information only, this
commit can be reverted.
|
|
|
|
itistoday> how do you specify multiple dependencies in a unit file? i've been
googling and can't find this basic thing :-\
itistoday> do you use a comma, or use multiple After= statements?
|
|
|
|
|
|
This reverts commit adcf4c81c58511b67644e17fa743d1729d3c9ccf.
We have a better solution for the problem of making two processes run in
the same namespace, and --listener is not needed hence and should be
dropped.
Conflicts:
man/systemd-socket-proxyd.xml
|
|
This reverts commit adcf4c81c58511b67644e17fa743d1729d3c9ccf.
We have a better solution for the problem of making two processes run in
the same namespace, and --listener is not needed hence and should be
dropped.
Conflicts:
man/systemd-socket-proxyd.xml
|
|
PrivateTmp= namespaces
|
|
|
|
the man page, given that it is detail information
|
|
Also, expose the new "flush" job mode this way.
|
|
setting and make use of it where applicable
|
|
This will allow specifying more options per address than the
simple Address= entry in the [Network] section.
Preliminary support for the same functionality for [Route] sections
are added, but not yet hooked up, as more testing is needed.
|
|
Use Description only internally, and allow Alias to be set
as a separate option. For instance SNMP uses ifalias for
a specific purpose, so let's not write to it by default.
|
|
This reverts commit fa7abba2328eb2d23a7e27708f86f5013059ddcf.
|
