summaryrefslogtreecommitdiff
path: root/man
Commit message (Collapse)AuthorAge
* man/os-release: Add BUILD_ID fieldWilliam Douglas2013-03-27
| | | | | BUILD_ID is a fairly generic field used to identify the system image that was used to install the distribution.
* Simplify the meaning of %sZbigniew Jędrzejewski-Szmek2013-03-26
| | | | | | | | | | | | | | | | | | | The rules governing %s where just too complicated. First of all, looking at $SHELL is dangerous. For systemd --system, it usually wouldn't be set. But it could be set if the admin first started a debug shell, let's say /sbin/sash, and then launched systemd from it. This shouldn't influence how daemons are started later on, so is better ignored. Similar reasoning holds for session mode. Some shells set $SHELL, while other set it only when it wasn't set previously (e.g. zsh). This results in fragility that is better avoided by ignoring $SHELL totally. With $SHELL out of the way, simplify things by saying that %s==/bin/sh for root, and the configured shell otherwise. get_shell() is the only caller, so it can be inlined. Fixes one issue seen with 'make check'.
* man: network.target is also a passive targetLennart Poettering2013-03-27
|
* man: document that the passive units cannot be pulled in mnaullyLennart Poettering2013-03-26
|
* man: properly document the system targets that are also available for the ↵Lennart Poettering2013-03-25
| | | | user instance
* man: rearrange systemd.special(7) to clarify which units are passive and ↵Lennart Poettering2013-03-25
| | | | | | which ones aren't This also adds a short explanation paragraph for this.
* units: introduce remote-fs-setup.target to pull in dependencies from remote ↵Lennart Poettering2013-03-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | mounts This introduces remote-fs-setup.target independently of remote-fs-pre.target. The former is only for pulling things in, the latter only for ordering. The new semantics: remote-fs-setup.target: is pulled in automatically by all remote mounts. Shall be used to pull in other units that want to run when at least one remote mount is set up. Is not ordered against the actual mount units, in order to allow activation of its dependencies even 'a posteriori', i.e. when a mount is established outside of systemd and is only picked up by it. remote-fs-pre.target: needs to be pulled in automatically by the implementing service, is otherwise not part of the initial transaction. This is ordered before all remote mount units. A service that wants to be pulled in and run before all remote mounts should hence have: a) WantedBy=remote-fs-setup.target -- so that it is pulled in b) Wants=remote-fs-pre.target + Before=remote-fs-pre.target -- so that it is ordered before the mount point, normally.
* units: introduce new timers.target and paths.target to hook timer/path units ↵Lennart Poettering2013-03-25
| | | | into for boot
* journal: Add sync timer to journal serverOleksii Shevchuk2013-03-25
| | | | | | | | Add option to force journal sync with fsync. Default timeout is 5min. Interval configured via SyncIntervalSec option at journal.conf. Synced journal files will be marked as OFFLINE. Manual sync can be performed via sending SIGUSR1.
* exec: Assigning the empty string to CapabilityBoundSet= should drop all capsLennart Poettering2013-03-22
| | | | | | | | | | Previously, it would set all caps, but it should drop them all, anything else makes little sense. Also, document that this works as it does, and what to do in order to assign all caps to the bounding set. https://bugzilla.redhat.com/show_bug.cgi?id=914705
* man/shutdown: /etc/nologin is called /run/nologin nowZbigniew Jędrzejewski-Szmek2013-03-21
|
* systemd-python: export sd_journal_get_usageZbigniew Jędrzejewski-Szmek2013-03-21
|
* man/service: document behaviour on failureZbigniew Jędrzejewski-Szmek2013-03-19
| | | | https://bugs.freedesktop.org/show_bug.cgi?id=38355
* journalct: beef up entry listingZbigniew Jędrzejewski-Szmek2013-03-19
| | | | The ability to dump catalog entries in full and by id is added.
* man/catalog: fix synopsis and remind to freeZbigniew Jędrzejewski-Szmek2013-03-19
|
* sd-journal: do not require path to be absoluteZbigniew Jędrzejewski-Szmek2013-03-18
| | | | | | Seems natural to be able to specify relative directory, e.g. with journalctl -D. And even if, this should be checked in front-end code, not in the library.
* udev: rename kernel command line option to net.ifnames=Kay Sievers2013-03-18
|
* man: udev - clarify when RUN is executedTom Gundersen2013-03-18
| | | | Unlike IMPORT and PROGRAM, RUN is not executed inline, but after all the rules of the given event have been processed.
* udev: net-name-slot - disable by kernel command line switchTom Gundersen2013-03-18
| | | | | | The properties will still be set in the udev database, but they will not be used for setting the interface names. As for the other kernel commandline switches, we allow it to be prefixed by 'rd.' to only apply in the initrd.
* man: udev - move documentation of configuration fileTom Gundersen2013-03-18
| | | | | Moved from udev(7) to systemd-udevd.service(8), where the rest of the documentation of the configuration of the daemon lives.
* man: udev - document 'builtin'Tom Gundersen2013-03-18
| | | | | The new IMPORT{builtin} and RUN{builtin} were not documented. Also make it clear that RUN= is really an alias for RUN{program}=.
* man: bootup - intrd-fs.target --> initrd.targetKay Sievers2013-03-16
|
* core: reuse the same /tmp, /var/tmp and inaccessible dirMichal Sekletar2013-03-15
| | | | | | | | All Execs within the service, will get mounted the same /tmp and /var/tmp directories, if service is configured with PrivateTmp=yes. Temporary directories are cleaned up by service itself in addition to systemd-tmpfiles. Directory which is mounted as inaccessible is created at runtime in /run/systemd.
* man: fix grammarZbigniew Jędrzejewski-Szmek2013-03-15
|
* systemd-activate: pass environment variables throughZbigniew Jędrzejewski-Szmek2013-03-15
| | | | | | | | | | | I need this to test half-installed socket-activated python script, which requires PYTHONPATH and LD_LIBRARY_PATH set. I assume that other people might find it useful to. -E VAR passes through VAR from the environment, while -E VAR=value sets VAR=value. systemd-activate -E PYTHONPATH=/var/tmp/inst1/usr/lib64/python3.3/site-packages -E LD_LIBRARY_PATH=/var/tmp/inst1/usr/lib -l 2000 python3 -c 'from systemd.daemon import listen_fds; print(listen_fds())'
* sd-booted: update sd_booted() check a bitLennart Poettering2013-03-15
| | | | | | | | | | | | | | | | | | | Previously we were testing whether /sys/fs/cgroup/systemd/ was a mount point. This might be problematic however, when the cgroup trees are bind mounted into a container from the host (which should be absolutely valid), which might create the impression that the container was running systemd, but only the host actually is. Replace this by a check for the existance of the directory /run/systemd/system/, which should work unconditionally, since /run can never be a bind mount but *must* be a tmpfs on systemd systems, which is flushed at boots. This means that data in /run always reflects information about the current boot, and only of the local container, which makes it the perfect choice for a check like this. (As side effect this is nice to Ubuntu people who now use logind with the systemd cgroup hierarchy, where the old sd_booted() check misdetects systemd, even though they still run legacy Upstart.)
* man: bootup - "Systemd in the Initrd" -> "Initrd System Manager Bootup"Kay Sievers2013-03-15
|
* Make initrd.target the default target in the initrdHarald Hoyer2013-03-15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | First, rename root-fs.target to initrd-root-fs.target to clarify its usage. Mount units with "x-initrd-rootfs.mount" are now ordered before initrd-root-fs.target. As we sometimes construct /sysroot mounts in /etc/fstab in the initrd, we want these to be mounted before the initrd-root-fs.target is active. initrd.target can be the default target in the initrd. (normal startup) : : v basic.target | ______________________/| / | | sysroot.mount | | | v | initrd-root-fs.target | | | v | initrd-parse-etc.service (custom initrd services) | | v | (sysroot-usr.mount and | various mounts marked | with fstab option | x-initrd.mount) | | | v | initrd-fs.target | | \______________________ | \| v initrd.target | v initrd-cleanup.service isolates to initrd-switch-root.target | v ______________________/| / | | initrd-udevadm-cleanup-db.service | | (custom initrd services) | | | \______________________ | \| v initrd-switch-root.target | v initrd-switch-root.service | v switch-root
* journalctl: show systemd messages about unit for -uZbigniew Jędrzejewski-Szmek2013-03-13
| | | | | | | | | | journalctl -u unit is not very useful, because it doesn't show systemd messages about starting, stopping, coredumps, etc, like systemctl status unit does. Make it show the same information using the same rules. If somebody really want to see just messages from by the unit, it is easy enough to use _SYSTEMD_UNIT=...
* man: fix some typosThomas Hindoe Paaboel Andersen2013-03-13
|
* add initrd-fs.target and root-fs.targetHarald Hoyer2013-03-13
| | | | | | | | | | | | | | Instead of using local-fs*.target in the initrd, use root-fs.target for sysroot.mount and initrd-fs.target for /sysroot/usr and friends. Using local-fs.target would mean to carry over the activated local-fs.target to the isolated initrd-switch-root.target and thus in the real root. Having local-fs.target already active after deserialization causes ordering problems with the real root services and targets. We better isolate to targets for initrd-switch-root.target, which are only available in the initrd.
* man: Document the actual behaviour of ExecStopPostMathieu Bridon2013-03-13
| | | | | | | | The documentation makes it sound like ExecStopPost is only run when stopping the service with `systemctl stop foo.service` However, that is not the case, as it also gets run when the service unexpectedly exists, crashes, or gets SIGKILLed.
* man,html: say 'systemd 198' in the headerZbigniew Jędrzejewski-Szmek2013-03-12
| | | | | | | This should help readers of the man or HTML pages know if the documentation is out of date. An alternative to use a date generated from 'git log' was considered, but since we try to keep user visible documentation up to date, showing the project version should be enough.
* man: strip the comments in man page headersZbigniew Jędrzejewski-Szmek2013-03-12
| | | | | They contained the date, which creates a problem with multiarch packages, since the generated file would be different each time.
* journalctl: imply -n1000 when -e is usedLennart Poettering2013-03-07
| | | | | Make sure the pager does not have to buffer an unbounded number of log messages, by default.
* man/*.html: link to directives, python, guvev, libudev in headersZbigniew Jędrzejewski-Szmek2013-03-07
| | | | | | | | Since the HTML files are in different directories during build and on fd.o, links are broken in the build directory. This could be fixed by moving stuff around, or by modifying the files during upload, but I think that people do not usually create HTML files for local browsing, and this is not necessary.
* pager: introduce "jump to end" optionHarald Hoyer2013-03-07
| | | | | | | | $ journalctl -be is what you want :) https://bugzilla.redhat.com/show_bug.cgi?id=867841
* TODO: python stuff and freeze and standbyZbigniew Jędrzejewski-Szmek2013-03-07
|
* bootchart: document -C, --cmdline parameterHarald Hoyer2013-03-07
|
* man: Unify title for configuration filesJan Janssen2013-03-07
|
* man: Fix id attributesJan Janssen2013-03-07
|
* man/kernel-install.xml: fix paths to reflect actual behaviourHarald Hoyer2013-03-07
|
* man: fix compilation of exampleZbigniew Jędrzejewski-Szmek2013-03-07
|
* journald: introduce new "systemd-journal" group and make it own the journal ↵Lennart Poettering2013-03-05
| | | | | | | | | | | | | | | | | | | | | files Previously all journal files were owned by "adm". In order to allow specific users to read the journal files without granting it access to the full "adm" powers, introduce a new specific group for this. "systemd-journal" has to be created by the packaging scripts manually at installation time. It's a good idea to assign a static UID/GID to this group, since /var/log/journal might be shared across machines via NFS. This commit also grants read access to the journal files by default to members of the "wheel" and "adm" groups via file system ACLs, since these "almost-root" groups should be able to see what's going on on the system. These ACLs are created by "make install". Packagers probably need to duplicate this logic in their postinst scripts. This also adds documentation how to grant access to the journal to additional users or groups via fs ACLs.
* build-sys: build and install systemd-coredumpctl conditionallyMichael Biebl2013-03-04
| | | | | If coredump support is disabled via --disable-coredump, do not build and install the systemd-coredumpctl binary and man page.
* build-sys: do not install pam_systemd(8) without PAMZbigniew Jędrzejewski-Szmek2013-03-04
|
* build-sys: do not install logind manpages when disabledZbigniew Jędrzejewski-Szmek2013-03-04
| | | | The condition was wrong: HAVE_PAM -> ENABLE_LOGIND.
* core/path: catch errors when adding watchesZbigniew Jędrzejewski-Szmek2013-03-03
| | | | | | | | | Errors because of oom conditions or descriptor exhaustion should not be ignored. We probably cannot recover from those conditions. Current behaviour wrt. insufficient permissions is described in the man page. It might make sense in case of user sessions, so I left it as is.
* journalctl: add --user-unit= switchDaniel Wallace2013-03-01
| | | | | Add --user-unit= to make it possible to query for user logs by the name of the service.
* journalctl: add --reverse option to show the newest lines firstLukas Nykryn2013-03-01
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-06 14:27:58 +0000