| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This is a recurring submission and includes corrections to various
issue spotted. I guess I can just skip over reporting ubiquitous
comma placement fixes…
Highligts in this particular commit:
- the "unsigned" type qualifier is completed to form a full type
"unsigned int"
- alphabetic -> lexicographic (that way we automatically define how
numbers get sorted)
|
| | |
|
| | |
|
| |
|
|
|
| |
Services using the watchdog option might want to be restarted
only if the watchdog triggers.
|
| |
|
|
|
| |
Can help since the journal requires /etc/machine-id to exists in order to start,
and will simply silently exit when it does not.
|
| | |
|
| |
|
|
|
|
| |
wait_filter() callback shouldn't process JobRemove signals for arbitrary
jobs. It should only deal with signals for jobs which are included in
set of jobs we wait for.
|
| | |
|
| |
|
|
| |
Fixup for ac4c8d6da8b5e.
|
| | |
|
| |
|
|
|
|
|
| |
This enables a getty on active kernel consoles even when they are not
the last one specified on the kernel command line and mapped to
/dev/console. Now the order "console=ttyS0 console=tty0" works in
addition to "console=tty0 console=ttyS0".
|
| |
|
|
| |
Contributed by Guillermo Dominguez Duarte <guillermod84@gmail.com>.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
bash allows them, and so should we.
string_has_cc is changed to allow tabs, and if they are not wanted,
they must be now checked for explicitly. There are two other callers,
apart from the env file loaders, and one already checked anyway, and
the other is changed to check.
https://bugs.freedesktop.org/show_bug.cgi?id=68592
https://bugs.gentoo.org/show_bug.cgi?id=481554
|
| |
|
|
|
|
| |
systemd-sysctl gives priority to the latest occurence as of commit
04bf3c1a60d82791e0320381e9268f727708f776, but the manpage hasn't been
updated for that.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
systemd-logind will start user@.service. user@.service unit uses
PAM with service name 'systemd-user' to perform account and session
managment tasks. Previously, the name was 'systemd-shared', it is
now changed to 'systemd-user'.
Most PAM installations use one common setup for different callers.
Based on a quick poll, distributions fall into two camps: those that
have system-auth (Redhat, Fedora, CentOS, Arch, Gentoo, Mageia,
Mandriva), and those that have common-auth (Debian, Ubuntu, OpenSUSE).
Distributions that have system-auth have just one configuration file
that contains auth, password, account, and session blocks, and
distributions that have common-auth also have common-session,
common-password, and common-account. It is thus impossible to use one
configuration file which would work for everybody. systemd-user now
refers to system-auth, because it seems that the approach with one
file is more popular and also easier, so let's follow that.
|
| |
|
|
| |
We don't allow reusing of scopes.
|
| |
|
|
|
| |
The VT number was already part of the DBus API, but was not
exposed in the C API.
|
| | |
|
| |
|
|
|
| |
When running from initrd, entering a wrong passphrase usually means that
you cannot boot. Therefore, we allow trying indefinitely.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
umount.target in the real root
These mounts should be kept around and unmounted in the shutdown ramfs.
Currently, we will still attempt to umount these in the final kill spree, but
we should consider avoiding that too. Also, the should_umount function should
be generalised and put into util.c or something like that, but we are still
discussing precisely how.
|
| |
|
|
|
|
|
| |
This makes mount units work like swap units: when the backing device appears
the mount unit will be started.
v2: the device should want the mount unconditionally, not only for DefaultDependencies=yes
|
| |
|
|
|
| |
There is no need to restrict this to only the 'nofail' case. In the '!nofail'
case the unit is already wanted by swap.target, so this is not a functional change.
|
| |
|
|
| |
This removes some redundancy between the generator and the core mount handling.
|
| |
|
|
|
|
|
| |
This means we can use default dependencies on mount units without having to get them automatically
ordered before the filesystem targets.
Reported-by: Thomas Baechler <thomas@archlinux.org>
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
This includes regularly-submitted corrections to comma setting and
orthographical mishaps that appeared in man/ in recent commits.
In this particular commit:
- the usual comma fixes
- expand contractions (this is prose)
|
| |
|
|
|
| |
We can use systemctl show unitname to show the BlockIODeviceWeight
of unit.
|
| |
|
|
|
|
|
| |
This patch allows user to set up BlockIODeviceWeight for unit
through systemctl. Such as
systemctl set-property sshd.service BlockIODeviceWeight="/dev/sda 100"
|
| |
|
|
|
|
| |
This patch adds the support for setting up BlockIODeviceWeight
in bus_cgroup_set_property. most of the codes are copied from
the case that sets up DeviceAllow.
|
| | |
|
| |
|
|
|
|
|
|
| |
This patch allows user to set up BlockIOReadBandwidth and BlockIOWriteBandwidth
for unit through systemctl. Such as
systemctl set-property sshd.service BlockIOReadBandwidth="/dev/sda 100000"
systemctl set-property sshd.service BlockIOWriteBandwidth="/dev/sda 200000"
|
| |
|
|
|
| |
This patch adds the support for setting up BlockIORead/WriteBandwidth
in bus_cgroup_set_property.
|
| |
|
|
|
| |
if we get BlockIOReadBandwidth="", we should only remove the
read-bandwidth-entries in blockio_device_bandwidths list.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
Vacuuming behaviour is a bit confusing, and/or we have some bugs,
so those additional messages should help to find out what's going
on. Also, rotation of journal files shouldn't be happening too
often, so the level of the messages is bumped to info, so that
they'll be logged under normal operation.
|
| |
|
|
|
| |
We need to override the TOUCHPAD_TOGGLE to F21 to make it useful under X, as
for other models.
|
| | |
|
| | |
|
| | |
|
| | |
|
