Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
Converted from html to xml and changed the style to fit into the other
manpages.
|
|
Note that there are still some rome for cleanups. In particular,
the .la files are now installed, which we probably don't want; and
some of the macros in Makefile.am are likely redundan.
|
|
Also update the licence in the source files.
|
|
|
|
|
|
The variable assignment operator was introduced in make 3.82 and thus
breaks "make install" with older versions of make. Since "=" is optional
in make 3.82 it is safe to drop.
|
|
|
|
|
|
Adding UNIT= to log lines allows them to be shown
in 'systemctl status' output, etc.
A new set of macros and functions is added. This allows for less
verbose notation than using log_struct() explicitly.
The set of logging functions is expanded to take a pair of arguments
(e.g. "UNIT=" and the RHS) which add an extra line to the structured
log entry. This can be used to add macros which add a different
identifier later on.
|
|
|
|
|
|
|
|
|
|
|
|
Actually, one might want to run valgrind even on optimized code.
Now the same check is used in the jenkins hash functions and
hashtable.
|
|
Just avoids repeating the same code a few times.
The way that hooks are named is standardized.
No functional change.
|
|
|
|
|
|
|
|
|
|
Commit c4eb236a2c didn't take into account the situation when the user
sets e.g. PYTHON=python3 (without the full path). This value would
then be used verbatim for PYTHON_BINARY and in she-bang lines in
scripts, which is incorrect. To fix this, $PYTHON is passed through
which, which expands the path. If $PYTHON_BINARY is desired which is
not installed on the build system, then PYTHON_BINARY must be set
separately.
|
|
When gobject-introspection-devel was not available, the message
was missing the yes/no part
|
|
Python binary to be used during compilation can be set with
./configure PYTHON=...
The she-bang line is removed, since it is not used anymore.
|
|
Python binary used in the she-bang line in installed
scripts can be set with ./configure PYTHON_BINARY=...
Defaults to the same path as python used during compilation.
Adding --version makes systemd-analyze behave consistently with the
rest of installed programs.
The lines in ./configure output are reordered to keep all yes/no lines
separate. I think that this makes the output clearer.
|
|
To be able to add --version and change python binary.
|
|
Commit 88516c0 removed one line too much.
|
|
|
|
|
|
|
|
Yay, we now have a completely generic systemd. No distribution specific checks anymore!
|
|
|
|
This Suse specific configuration file should really be done in a generator
that is shipped downstream by suse.
|
|
They don't really hurt on other distros, and this allows us to ship
the same code on all distros
|
|
sushell makes much less sense than sulogin. If distros want to stick to sushell
they should patch this downstream.
|
|
Since rc-local is now enabled via the SysV compatibility we should only refer
to it based on that too.
|
|
based on distro
|
|
Move forcefsck file checks under a HAVE_SYSV_COMPAT #ifdef, and warn if this is used.
|
|
|
|
This also drops automatic selection of the rc local scripts
based on the local distro. Distributions now should specify the paths
of the rc-local and halt-local scripts on the configure command line.
|
|
hostname, locale, timezone
This simplifies the upstream system code quite a bit. If downstream distributions want to maintain compatibility with their old configuration files, they are welcome to do so, but need to maintain this as patches downstream. The burden needs to be on the distributions to maintain differences here. Our suggestion however is to just convert the old configuration files on upgrade, as multiple distributions already do.
|
|
|
|
|
|
This patch allows globbing to be used with EnvironmentFile option.
Example:
EnvironmentFile=/etc/foo.d/*.conf
t. Pekka
|
|
Adds is-failed to join is-active and is-enabled.
I grabbed this one from the todo list. Most of the functionality was
already there for is-active. I just needed to make check_one_unit take
the states to check for as an argument instead of the hardcoded
"active" and "reloading".
is-failed will return 1 if none of the units given are failed. This is
different from is-active which will return 3 if none of the units
given are active. It returns 3 with this comment:
/* According to LSB: "program is not running" */
As that does not make sense when looking for failed units I simply
chose 1 instead.
|
|
There is no parameter named luks.fstab.
|
|
Use mkdir_p_label instead of mkdir_parents_label, so that the final
directory component is created too.
|
|
|