| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Lennart has convinced me that it's more helpful to participate than to sit
on the sidelines and complain. So, hello everyone.
I'm starting by giving up the battle to change the systemctl "isolate"
command to "switch-to". Can't win them all. :) I've got a suggested patch
to expand the documentation a bit, hopefully making it more clear to new
systemd users.
Is there an easy way to list all units where AllowIsolate is enabled? That
should be included alongside this, I think.
|
| |
|
|
|
|
|
| |
This change makes sure that our output never exceeds 80ch on 80ch
terminals.
https://bugzilla.redhat.com/show_bug.cgi?id=626443
|
| |
|
|
|
|
| |
This replaces OOMAdjust= by OOMScoreAdjust= in the config files,
breaking compatibility with older unit files. However, this keeps compat
with older kernels which lack the new OOM rework.
|
| |
|
|
| |
https://bugzilla.redhat.com/show_bug.cgi?id=614619
|
| | |
|
| |
|
|
|
| |
This requires the /sys/fs/cgroup to exist. Current git kernels have
this, released kernels need a backport of a single patch.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
non-ro root dirs
Instead of using /forcefsck and /fastboot people should just kernel
command line options to achieve the same.
|
| |
|
|
|
|
|
| |
That should friendlier for folks who just run "shutdown" to figure out
the command line arguments...
https://bugzilla.redhat.com/show_bug.cgi?id=624149
|
| | |
|
| |
|
|
| |
services
|
| |
|
|
|
|
|
|
|
|
| |
lines for oneshot services
In contrast to the other service types oneshot services are usually not
long lasting and there's not necessarily a single clean main process for
them. This change allows multiple ExecStart= lines for this type of
services so that the admin/developer doesn't have to arbitrarily pick on
of various sequential commands as the "main one".
|
| | |
|
| |
|
|
|
|
|
|
| |
RefuseManualStop=
Some unit shall never be start on user request (e.g. shutdown.target)
others never be stopped on user request (e.g. auditd.servce), hence
offer options for both.
|
| |
|
|
|
|
|
| |
remove the one that is "conflicted"
This gives the writer of units control which unit is kept and which is
stopped when two units conflict.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Hi,
attached path extends socket configurables with another
knob - TCP Congestion Avoidance selection. Linux implements
handful of those, useful in various situations. For example,
TCP Low Priority may be used by FTP service to gracefully
yield bandwidth for more important TCP/IP streams.
Until recently TCP_CONGESTION was Linux-specific, recently
FreeBSD 8 and OpenSolaris gained compatible support.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
seperate arguments
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Don't try to merge devices that have been created via dependencies when
they appear in the system and can be recognized as the same. Instead,
simply continue to maintain them independently of each other, however
with the same state cycle. Why? Because otherwise we'd have a hard time
to seperate the dependencies after the devices are unplugged again and
we hence cannot be sure anymore that next time the device is plugged in
it will carry the same names.
Example: if one depndency refers to dev-sda.device and another one to
dev-by-id-xxxyyy.device we only learn at time of plug in of the device
that it is actually the same device that was ment. In the moment the
device is unplugged again we won't know anymore their relation to each
other and the next time the harddisk is plugged it might even appear as
dev-by-id-xxxyyy.device and dev-sdb.service. To ensure the dependencies
continue to have the meaning they were intended to have let's hence keep
the .device objects seperate all the time, even when they are plugged
in.
This patch also introduces a new Following= property which points from
the various .device units of a specific device to the main .device unit
for it. This can be used by the client side to figure out the relation
of the .device units to each other and even filter units from display.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
and D-Bus
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
file is now shipped upstream dbus
|
| | |
|
| |
|
|
| |
Fix some minor grammar and punctuation typos.
|
| |
|
|
| |
Fix minor typographic, punctuation and grammar errors.
|
| |
|
|
|
|
|
|
|
|
| |
Rename --start to --realize, to make things less confusing when doing
"systemctl stop --realize foo.service".
Introduce --realize=reload.
Don't talk to systemd when run within a chroot, or when systemd isn't
running.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
systemd.exec, systemd, and systemd.timer pages
Just some minor grammar fixes.
|
| | |
|
