summaryrefslogtreecommitdiffstats
path: root/Makefile-man.am (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #5131 from keszybz/environment-generatorsLennart Poettering2017-02-211-0/+11
|\ | | | | Environment generators
| * build-sys,man: load /etc/environment and describe the new environment.d syntaxRay Strode2017-02-211-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | Add support for /etc/environment and document the changes to the user manager to automatically import environment *.conf files from: ~/.config/environment.d/ /etc/environment.d/ /run/environment.d/ /usr/local/lib/environment.d/ /usr/lib/environment.d/ /etc/environment
| * environment-generator: new generator to peruse environment.dZbigniew Jędrzejewski-Szmek2017-02-211-0/+7
| | | | | | | | | | | | | | | | Why the strange name: the prefix is necessary to follow our own advice that environment generators should have numerical prefixes. I also put -d- in the name because otherwise the name was very easy to mistake with systemd.environment-generator. This additional letter clarifies that this on special generator that supports environment.d files.
| * man: add systemd.environment-generator(7) with two examplesZbigniew Jędrzejewski-Szmek2017-02-211-0/+2
| | | | | | | | | | | | | | | | | | v2: - add example files to EXTRA_DIST v3: - rework for the new scheme where nothing is written to disk v4: - use separate dirs for system and user env generators
* | tree-wide: add SD_ID128_MAKE_STR, remove LOG_MESSAGE_IDZbigniew Jędrzejewski-Szmek2017-02-151-0/+5
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Embedding sd_id128_t's in constant strings was rather cumbersome. We had SD_ID128_CONST_STR which returned a const char[], but it had two problems: - it wasn't possible to statically concatanate this array with a normal string - gcc wasn't really able to optimize this, and generated code to perform the "conversion" at runtime. Because of this, even our own code in coredumpctl wasn't using SD_ID128_CONST_STR. Add a new macro to generate a constant string: SD_ID128_MAKE_STR. It is not as elegant as SD_ID128_CONST_STR, because it requires a repetition of the numbers, but in practice it is more convenient to use, and allows gcc to generate smarter code: $ size .libs/systemd{,-logind,-journald}{.old,} text data bss dec hex filename 1265204 149564 4808 1419576 15a938 .libs/systemd.old 1260268 149564 4808 1414640 1595f0 .libs/systemd 246805 13852 209 260866 3fb02 .libs/systemd-logind.old 240973 13852 209 255034 3e43a .libs/systemd-logind 146839 4984 34 151857 25131 .libs/systemd-journald.old 146391 4984 34 151409 24f71 .libs/systemd-journald It is also much easier to check if a certain binary uses a certain MESSAGE_ID: $ strings .libs/systemd.old|grep MESSAGE_ID MESSAGE_ID=%02x%02x%02x%02x%02x%02x%02x%02x%02x%02x%02x%02x%02x%02x%02x%02x MESSAGE_ID=%02x%02x%02x%02x%02x%02x%02x%02x%02x%02x%02x%02x%02x%02x%02x%02x MESSAGE_ID=%02x%02x%02x%02x%02x%02x%02x%02x%02x%02x%02x%02x%02x%02x%02x%02x MESSAGE_ID=%02x%02x%02x%02x%02x%02x%02x%02x%02x%02x%02x%02x%02x%02x%02x%02x $ strings .libs/systemd|grep MESSAGE_ID MESSAGE_ID=c7a787079b354eaaa9e77b371893cd27 MESSAGE_ID=b07a249cd024414a82dd00cd181378ff MESSAGE_ID=641257651c1b4ec9a8624d7a40a9e1e7 MESSAGE_ID=de5b426a63be47a7b6ac3eaac82e2f6f MESSAGE_ID=d34d037fff1847e6ae669a370e694725 MESSAGE_ID=7d4958e842da4a758f6c1cdc7b36dcc5 MESSAGE_ID=1dee0369c7fc4736b7099b38ecb46ee7 MESSAGE_ID=39f53479d3a045ac8e11786248231fbf MESSAGE_ID=be02cf6855d2428ba40df7e9d022f03d MESSAGE_ID=7b05ebc668384222baa8881179cfda54 MESSAGE_ID=9d1aaa27d60140bd96365438aad20286
* build-sys,man: describe systemd-umount and hook it up to installation (#5227)Zbigniew Jędrzejewski-Szmek2017-02-051-0/+5
|
* verity: add support for setting up verity-protected root disks in the initrdLennart Poettering2016-12-211-2/+11
| | | | | | | | | This adds a generator and a small service that will look for "roothash=" on the kernel command line and use it for setting up a very partition for the root device. This provides similar functionality to nspawn's existing --roothash= switch.
* fstab-generator: add support for volatile bootsLennart Poettering2016-12-211-0/+7
| | | | | | | | | | | | | | | | | | | | This adds support for a new kernel command line option "systemd.volatile=" that provides the same functionality that systemd-nspawn's --volatile= switch provides, but for host systems (i.e. systems booting with a kernel). It takes the same parameter and has the same effect. In order to implement systemd.volatile=yes a new service systemd-volatile-root.service is introduced that only runs in the initrd and rearranges the root directory as needed to become a tmpfs instance. Note that systemd.volatile=state is implemented different: it simply generates a var.mount unit file that is part of the normal boot and has no effect on the initrd execution. The way this is implemented ensures that other explicit configuration for /var can always override the effect of these options. Specifically, the var.mount unit is generated in the "late" generator directory, so that it only is in effect if nothing else overrides it.
* Add sd_is_socket_sockaddr (#4885)Zbigniew Jędrzejewski-Szmek2016-12-141-0/+5
| | | Fixes #1188.
* sd-id128: add new sd_id128_get_machine_app_specific() APILennart Poettering2016-11-291-0/+5
| | | | | | | | | | | | This adds an API for retrieving an app-specific machine ID to sd-id128. Internally it calculates HMAC-SHA256 with an 128bit app-specific ID as payload and the machine ID as key. (An alternative would have been to use siphash for this, which is also cryptographically strong. However, as it only generates 64bit hashes it's not an obvious choice for generating 128bit IDs.) Fixes: #4667
* man: add journal-upload.conf(5)Zbigniew Jędrzejewski-Szmek2016-10-161-0/+7
| | | | Fixes #3370.
* man: update sd-id128(3) a bitLennart Poettering2016-10-071-0/+10
| | | | | | Let's add documentation about SD_ID128_NULL and sd_id128_is_null(). Let's also indent our examples by 8chs, as is generally our coding style.
* core: add "invocation ID" concept to service managerLennart Poettering2016-10-071-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds a new invocation ID concept to the service manager. The invocation ID identifies each runtime cycle of a unit uniquely. A new randomized 128bit ID is generated each time a unit moves from and inactive to an activating or active state. The primary usecase for this concept is to connect the runtime data PID 1 maintains about a service with the offline data the journal stores about it. Previously we'd use the unit name plus start/stop times, which however is highly racy since the journal will generally process log data after the service already ended. The "invocation ID" kinda matches the "boot ID" concept of the Linux kernel, except that it applies to an individual unit instead of the whole system. The invocation ID is passed to the activated processes as environment variable. It is additionally stored as extended attribute on the cgroup of the unit. The latter is used by journald to automatically retrieve it for each log logged message and attach it to the log entry. The environment variable is very easily accessible, even for unprivileged services. OTOH the extended attribute is only accessible to privileged processes (this is because cgroupfs only supports the "trusted." xattr namespace, not "user."). The environment variable may be altered by services, the extended attribute may not be, hence is the better choice for the journal. Note that reading the invocation ID off the extended attribute from journald is racy, similar to the way reading the unit name for a logging process is. This patch adds APIs to read the invocation ID to sd-id128: sd_id128_get_invocation() may be used in a similar fashion to sd_id128_get_boot(). PID1's own logging is updated to always include the invocation ID when it logs information about a unit. A new bus call GetUnitByInvocationID() is added that allows retrieving a bus path to a unit by its invocation ID. The bus path is built using the invocation ID, thus providing a path for referring to a unit that is valid only for the current runtime cycleof it. Outlook for the future: should the kernel eventually allow passing of cgroup information along AF_UNIX/SOCK_DGRAM messages via a unique cgroup id, then we can alter the invocation ID to be generated as hash from that rather than entirely randomly. This way we can derive the invocation race-freely from the messages.
* man: document sd_bus_track objectsLennart Poettering2016-08-221-0/+89
| | | | | | And while ware at it, also drop some references to kdbus, and stop claiming sd-bus wasn't stable yet. Also order man page references in the main sd-bus man page alphabetically.
* add a new tool for creating transient mount and automount unitsLennart Poettering2016-08-181-0/+2
| | | | | | | | | | | | | | | | | | | | | | | This adds "systemd-mount" which is for transient mount and automount units what "systemd-run" is for transient service, scope and timer units. The tool allows establishing mounts and automounts during runtime. It is very similar to the usual /bin/mount commands, but can pull in additional dependenices on access (for example, it pulls in fsck automatically), an take benefit of the automount logic. This tool is particularly useful for mount removable file systems (such as USB sticks), as the automount logic (together with automatic unmount-on-idle), as well as automatic fsck on first access ensure that the removable file system has a high chance to remain in a fully clean state even when it is unplugged abruptly, and returns to a clean state on the next re-plug. This is a follow-up for #2471, as it adds a simple client-side for the transient automount logic added in that PR. In later work it might make sense to invoke this tool automatically from udev rules in order to implement a simpler and safer version of removable media management á la udisks.
* nss: add new "nss-systemd" NSS module for mapping dynamic usersLennart Poettering2016-07-221-0/+7
| | | | | With this NSS module all dynamic service users will be resolvable via NSS like any real user.
* sd-event: expose the event loop iteration counter via ↵Lennart Poettering2016-06-301-0/+5
| | | | | | | | | | | sd_event_get_iteration() (#3631) This extends the existing event loop iteration counter to 64bit, and exposes it via a new function sd_event_get_iteration(). This is helpful for cases like issue #3612. After all, since we maintain the counter anyway, we might as well expose it. (This also fixes an unrelated issue in the man page for sd_event_wait() where micro and milliseconds got mixed up)
* man: document some sd-bus functions (#3567)mahkoh2016-06-211-0/+8
| | | | | | * sd_bus_add_match * sd_bus_get_fd * sd_bus_message_read_basic * sd_bus_process
* man: document the new by-fd journal callsLennart Poettering2016-04-251-4/+14
| | | | | Also, remove documentation for sd_journal_open_container() as we consider it deprecated now.
* Merge pull request #2944 from keszybz/man-coredump-sysctlLennart Poettering2016-04-061-1/+11
|\ | | | | Man coredump sysctl
| * man: also mention systemd-coredump@.service and systemd-coredump.socketZbigniew Jędrzejewski-Szmek2016-04-061-1/+11
| | | | | | | | Added in 3c171f0b1e.
| * DHCP DUID, IAID configuration optionsVinay Kulkarni2016-03-311-0/+7
| |
| * Revert "DHCP DUID and IAID configurability"Zbigniew Jędrzejewski-Szmek2016-03-211-7/+0
| |
* | man: import "Implementing Offline System Updates"Zbigniew Jędrzejewski-Szmek2016-03-161-0/+2
|/ | | | | | | This imports most of http://www.freedesktop.org/wiki/Software/systemd/SystemUpdates/ to turn it into a man page. Similarly for the man page about generators, this will make it easier to keep up-to-date, keep a history of changes, and make it more discoverable for end-users.
* DHCP DUID and IAID configurabilityVinay Kulkarni2016-03-101-0/+7
|
* Merge pull request #2664 from zonque/bootchart-removalLennart Poettering2016-02-231-14/+0
|\ | | | | Remove systemd-bootchart
| * Remove systemd-bootchartDaniel Mack2016-02-231-14/+0
| | | | | | | | | | | | | | This commit rips out systemd-bootchart. It will be given a new home, outside of the systemd repository. The code itself isn't actually specific to systemd and can be used without systemd even, so let's put it somewhere else.
* | man: add minimal man page for systemd-importd.serviceLennart Poettering2016-02-231-0/+12
|/
* Merge pull request #2618 from zonque/busproxy-removalLennart Poettering2016-02-151-9/+0
|\ | | | | remove bus-proxyd
| * remove bus-proxydDaniel Mack2016-02-121-9/+0
| | | | | | | | | | | | | | | | | | | | As kdbus won't land in the anticipated way, the bus-proxy is not needed in its current form. It can be resurrected at any time thanks to the history, but for now, let's remove it from the sources. If we'll have a similar tool in the future, it will look quite differently anyway. Note that stdio-bridge is still available. It was restored from a version prior to f252ff17, and refactored to make use of the current APIs.
* | Promote systemd-activate to /usr/bin/systemd-socket-activateZbigniew Jędrzejewski-Szmek2016-02-151-2/+2
|/ | | | | | | It has fairly wide functionality now and the interface has been stable for a while. It it a useful testing tool. The name is changed to better indicate what it does.
* sd-journal: add an API to enumerate known field names of the journalLennart Poettering2016-02-011-0/+12
| | | | | | This adds two new calls to get the list of all journal fields names currently in use. This is the low-level support to implement the feature requested in #2176 in a more optimized way.
* sd-journal: introduce has_runtime_files and has_persistent_filesJan Synacek2016-02-011-0/+7
| | | | | | | Also introduce sd_journal_has_runtime_files() and sd_journal_has_persistent_files() to the public API. These functions can be used to easily find out if the open journal files are runtime and/or persistent.
* man: add stub sd-bus(3)Zbigniew Jędrzejewski-Szmek2016-01-261-0/+2
| | | | | | | | | | | | | | | | | | | | | | We have 126 broken links to sd-bus.html, it's nice to fix that. Current version is mostly a stub, with a long list of links to other pages. I think that's fine, especially that sd-bus might evolve quite a bit before it is made public. Not all of linked pages are written. Still missing: sd_bus_can_send sd_bus_get_name_creds sd_bus_get_owner_creds sd_bus_message_can_send sd_bus_message_get_creds sd_bus_message_set_allow_interactive_authorization sd_bus_send sd_bus_set_address sd_bus_set_description sd_bus_start sd_event_set_prepare sd-device systemd.busname
* man: document systemd-resolve(8)Lennart Poettering2016-01-251-0/+2
| | | | This also links up the new manpage from systemd-resolved.service(8), and makes a couple of unrelated additions.
* man: add documentation for dnssec-trust-anchors.d(5)Lennart Poettering2016-01-051-1/+13
|
* tree-wide: expose "p"-suffix unref calls in public APIs to make gcc cleanup easyLennart Poettering2015-11-271-0/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | GLIB has recently started to officially support the gcc cleanup attribute in its public API, hence let's do the same for our APIs. With this patch we'll define an xyz_unrefp() call for each public xyz_unref() call, to make it easy to use inside a __attribute__((cleanup())) expression. Then, all code is ported over to make use of this. The new calls are also documented in the man pages, with examples how to use them (well, I only added docs where the _unref() call itself already had docs, and the examples, only cover sd_bus_unrefp() and sd_event_unrefp()). This also renames sd_lldp_free() to sd_lldp_unref(), since that's how we tend to call our destructors these days. Note that this defines no public macro that wraps gcc's attribute and makes it easier to use. While I think it's our duty in the library to make our stuff easy to use, I figure it's not our duty to make gcc's own features easy to use on its own. Most likely, client code which wants to make use of this should define its own: #define _cleanup_(function) __attribute__((cleanup(function))) Or similar, to make the gcc feature easier to use. Making this logic public has the benefit that we can remove three header files whose only purpose was to define these functions internally. See #2008.
* man: fully document sd-event interfacesLennart Poettering2015-11-191-5/+194
| | | | | | | | | This completes the set of man pages for sd-event and contains some minor other fixes for other man pages too. The sd_event_set_name(3) man page is renamed to sd_event_source_set_description(3), which is the correct name of the concept today.
* Remove snapshot unit typeZbigniew Jędrzejewski-Szmek2015-11-111-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | Snapshots were never useful or used for anything. Many systemd developers that I spoke to at systemd.conf2015, didn't even know they existed, so it is fairly safe to assume that this type can be deleted without harm. The fundamental problem with snapshots is that the state of the system is dynamic, devices come and go, users log in and out, timers fire... and restoring all units to some state from the past would "undo" those changes, which isn't really possible. Tested by creating a snapshot, running the new binary, and checking that the transition did not cause errors, and the snapshot is gone, and snapshots cannot be created anymore. New systemctl says: Unknown operation snapshot. Old systemctl says: Failed to create snapshot: Support for snapshots has been removed. IgnoreOnSnaphost settings are warned about and ignored: Support for option IgnoreOnSnapshot= has been removed and it is ignored http://lists.freedesktop.org/archives/systemd-devel/2015-November/034872.html
* Merge pull request #1542 from keszybz/journal-audit-optionalLennart Poettering2015-10-131-0/+5
|\ | | | | Make journald audit socket maskable
| * Document journald sockets paths a bit moreZbigniew Jędrzejewski-Szmek2015-10-121-0/+5
| | | | | | | | | | | | Adding them to the documentation makes it easier to find the right man page for people who are trying to understand where some socket in the filesystem is coming from.
* | core: add support for naming file descriptors passed using socket activationLennart Poettering2015-10-061-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds support for naming file descriptors passed using socket activation. The names are passed in a new $LISTEN_FDNAMES= environment variable, that matches the existign $LISTEN_FDS= one and contains a colon-separated list of names. This also adds support for naming fds submitted to the per-service fd store using FDNAME= in the sd_notify() message. This also adds a new FileDescriptorName= setting for socket unit files to set the name for fds created by socket units. This also adds a new call sd_listen_fds_with_names(), that is similar to sd_listen_fds(), but also returns the names of the fds. systemd-activate gained the new --fdname= switch to specify a name for testing socket activation. This is based on #1247 by Maciej Wereski. Fixes #1247.
* | rfkill: rework and make it listen on /dev/rfkillLennart Poettering2015-10-011-5/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | With this rework we introduce systemd-rfkill.service as singleton that is activated via systemd-rfkill.socket that listens on /dev/rfkill. That way, we get notified each time a new rfkill device shows up or changes state, in which case we restore and save its current setting to disk. This is nicer than the previous logic, as this means we save/restore state even of rfkill devices that are around only intermittently, and save/restore the state even if the system is shutdown abruptly instead of cleanly. This implements what I suggested in #1019 and obsoletes it.
* | machine-id-commit: merge machine-id-commit functionality into machine-id-setupLennart Poettering2015-09-291-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | And remove machine-id-commit as separate binary. There's really no point in keeping this separate, as the sources are pretty much identical, and have pretty identical interfaces. Let's unify this in one binary. Given that machine-id-commit was a private binary of systemd (shipped in /usr/lib/) removing the tool is not an API break. While we are at it, improve the documentation of the command substantially.
* | sd-bus: add sd_bus_path_{encode,decode}_many()David Herrmann2015-09-261-0/+10
| | | | | | | | | | | | | | This introduces two new helpers alongside sd_bus_path_{encode,decode}(), which work similarly to their counterparts, but accept a format-string as input. This allows encoding and decoding multiple labels of a format string at the same time.
* | nspawn: add new .nspawn files for container settingsLennart Poettering2015-09-061-0/+2
| | | | | | | | | | | | | | .nspawn fiels are simple settings files that may accompany container images and directories and contain settings otherwise passed on the nspawn command line. This provides an efficient way to attach execution data directly to containers.
* | sd-login: add new sd_pid_get_cgroup() APILennart Poettering2015-09-051-0/+10
| | | | | | | | | | | | | | | | | | | | This adds a new sd_pid_get_cgroup() call to sd-login which may be used to query the control path of a process. This is useful for programs when making use of delegation units, in order to figure out which subtree has been delegated. In light of the unified control group hierarchy this is finally safe to do, hence let's add a proper API for it, to make it easier to use this.
* | man: document nss-resolveLennart Poettering2015-08-261-0/+7
| |
* | gpt-auto-generator: merge efi-boot-generatorKay Sievers2015-07-291-2/+0
|/
* man: document user slice sd-login calls we added a while backLennart Poettering2015-07-081-0/+10
|
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-11 13:36:25 +0100