summaryrefslogtreecommitdiff
path: root/man
AgeCommit message (Collapse)Author
2012-11-15Isolation of udev code from remaining systemdAnthony G. Basile
This commit is a first attempt to isolate the udev code from the remaining code base. It intentionally does not modify any files but purely delete files which, on a first examination, appear to not be needed. This is a sweeping commit which may easily have missed needed code. Files can be retrieved by doing a checkout from the previous commit: git checkout 2944f347d0 -- <filename>
2012-11-14man: throw in an example of timedatectl outputZbigniew Jędrzejewski-Szmek
timedatectl is too cool not to advertise it a bit.
2012-11-12systemd-delta.xml: document default value for --diffThomas Hindoe Paaboel Andersen
2012-11-11man/sd-id128.xml: typo fixHolger Hans Peter Freyther
2012-11-06man: typo fixes for new files in 195Thomas Hindoe Paaboel Andersen
2012-11-06Revert "Implement SocketUser= and SocketGroup= for [Socket]"Dave Reisner
This was never intended to be pushed. This reverts commit aea54018a5e66a41318afb6c6be745b6aef48d9e.
2012-11-05Implement SocketUser= and SocketGroup= for [Socket]Dave Reisner
Since we already allow defining the mode of AF_UNIX sockets and FIFO, it makes sense to also allow specific user/group ownership of the socket file for restricting access.
2012-11-05systemd.socket.xml: fix typoDave Reisner
2012-11-01man: typo fixesThomas Hindoe Paaboel Andersen
Fixes a few more typos. Also changes a "Accept=no" to "Accept=false" to be consistent with the previous examples in the same man page.
2012-10-31service: drop special HTTP server target, as it is a bad idea anf Fedora ↵Lennart Poettering
specific This was premarily intended to support the LSB facility $httpd which is only known by Fedora, and a bad idea since it lacks any real-life usecase. Similar, drop support for some other old Fedora-specific facilities. Also, document the rules for introduction of new facilities, to clarify the situation for the future.
2012-10-31man: explain a bit more detailed what happens on suspendLennart Poettering
2012-10-31man: document that Documentation= follows an orderLennart Poettering
2012-10-30coredumpctl: add --field/-F optionZbigniew Jędrzejewski-Szmek
Useful for completion generation.
2012-10-30coredumpctl: add --no-legend optionZbigniew Jędrzejewski-Szmek
Useful for completion generation.
2012-10-30SMACK: Add configuration options. (v3)Auke Kok
This adds SMACK label configuration options to socket units. SMACK labels should be applied to most objects on disk well before execution time, but two items remain that are generated dynamically at run time that require SMACK labels to be set in order to enforce MAC on all objects. Files on disk can be labelled using package management. For device nodes, simple udev rules are sufficient to add SMACK labels at boot/insertion time. Sockets can be created at run time and systemd does just that for several services. In order to protect FIFO's and UNIX domain sockets, we must instruct systemd to apply SMACK labels at runtime. This patch adds the following options: Smack - applicable to FIFO's. SmackIpIn/SmackIpOut - applicable to sockets. No external dependencies are required to support SMACK, as setting the labels is done using fsetxattr(). The labels can be set on a kernel that does not have SMACK enabled either, so there is no need to #ifdef any of this code out. For more information about SMACK, please see Documentation/Smack.txt in the kernel source code. v3 of this patch changes the config options to be CamelCased.
2012-10-28logind: add 'lock' as possible choice for handling hw keysLennart Poettering
2012-10-28udev: add "udevadm hwdb --test=<modalias>"Kay Sievers
2012-10-28man/logind.conf.xml: Add missing 'suspend' value for Handle*Key options.Thomas Bächler
2012-10-28logind: support for hybrid sleep (i.e. suspend+hibernate at the same time)Lennart Poettering
2012-10-27coredumpctl: add 'gdb' verb to start gdb right-away on a collected coredumpLennart Poettering
2012-10-26journal: provide an API that allows client to figure out whether they need ↵Lennart Poettering
to recheck the journal manually for changes in regular intervals Network file systems generally do not offer inotify() that would work across the network. We hence cannot rely on inotify() exclusiely in those case. Provide an API to determine these cases, and suggest doing manual regular rechecks. Note that this is not complete yet, as we need to rescan journal dirs on network file systems explicitly to find new/removed files
2012-10-26man: minor updatesLennart Poettering
2012-10-26man: fix exampleLennart Poettering
2012-10-26man: typo fixesThomas Hindoe Paaboel Andersen
https://bugs.freedesktop.org/show_bug.cgi?id=55890 Fixed typos, serial comma, and removed "either" as there were more than two options. Also did an extra rename of "system-shutdown" to "systemd-shutdown" that was forgotten in commit 8bd3b8620c80d0f2383f2fb04315411fc8077ca1
2012-10-25journal: properly serialize fields with multiple values into JSONLennart Poettering
This now matches the JSON serialization spec from: http://www.freedesktop.org/wiki/Software/systemd/json
2012-10-24man: udev - add 'udevadm hwdb --update'Kay Sievers
2012-10-23man: fix typo in tmpfiles.dTom Gundersen
Reported-by: Jason St. John <jstjohn@purdue.edu>
2012-10-23tmpfiles: allow Age to be set to 0Tom Gundersen
Mostly useful for testing purposes. Setting Age to 1s works just as well, but it is surprising that using 0s (or just 0) does not work. Also clarify this in the documentation.
2012-10-23man: reword journalctl -n descriptionZbigniew Jędrzejewski-Szmek
2012-10-23man: the corresponding LSB facility to rpcbind.target is $portmapMichael Biebl
2012-10-21man: add man page for localectlLennart Poettering
2012-10-19journal: add tool to extract coredumpsZbigniew Jędrzejewski-Szmek
'systemd-coredumpctl' will list available coredumps: PID UID GID sig exe 32452 500 500 11 /home/zbyszek/systemd/build/journalctl 32666 500 500 11 /usr/lib64/valgrind/memcheck-amd64-linux ... 'systemd-coredumpctl dump PID' will write the coredump to specified file or stdout.
2012-10-19journald.conf: remove MinSize= settingsLennart Poettering
There's no point in making this configurable, so let's drop it in order to simplify configuration a bit.
2012-10-19systemctl: remove --follow optionLennart Poettering
Given that "journalctl -u" exists now there's no need to duplicate this functionality in systemctl, so let's drop this, especially given that it always felt a bit awkward to overload "-f" to both --force and --follow, and to have continues output with a status header for this. systemctl status -f avahi-daemon now becomes: journalctl -fu avahi-daemon Which is shorter and a lot less redundant.
2012-10-18man: fix compilation warning in sd_journal_query_unique exampleZbigniew Jędrzejewski-Szmek
2012-10-18man: ensure example of sd_journal_query_unique() compiles cleanlyLennart Poettering
2012-10-18journalctl.xml: fix shortopt for --fieldDave Reisner
2012-10-18man: add missing man pageLennart Poettering
2012-10-18journalctl: implement quering field values with new -F switchLennart Poettering
Example: journalctl -F _SYSTEMD_UNIT will list all units that ever logged to the journal.
2012-10-18journal: add ability to list values a specified field can take in all ↵Lennart Poettering
entries of the journal The new 'unique' API allows listing all unique field values that a field specified by a field name can take in all entries of the journal. This allows answering queries such as "What units logged to the journal?", "What hosts have logged into the journal?", "Which boot IDs have logged into the journal?". Ultimately this allows implementation of tools similar to lastlog based on journal data. Note that listing these field values will not work for journal files created with older journald, as the field values are not indexed in older files.
2012-10-18manager: connect SIGRTMIN+24 to terminating --user instancesLennart Poettering
2012-10-18service: when invoking service processes in --user mode set MANAGERPID to ↵Lennart Poettering
PID of systemd
2012-10-17timedatectl: rename --fix-system to --adjust-system-clockLennart Poettering
Quite long to read but hopefully less misleading.
2012-10-17hostname: add new hostnamectl tool as text client for hostnamedLennart Poettering
2012-10-17timedatectl: introduce new command line client for timedatedLennart Poettering
Much like logind has a client in loginctl, and journald in journalctl introduce timedatectl, to change the system time (incl. RTC), timezones and related settings.
2012-10-16journal: implement time-based rotation/vacuumingLennart Poettering
This also enables time-based rotation (but not vacuuming) after 1month, so that not more one month of journal is lost at a time per vacuuming.
2012-10-16id128: introduce new SD_ID128_CONST_STR() macroLennart Poettering
2012-10-16journalctl: add --unit=/-u to match by unit nameLennart Poettering
This applies unit_name_mangle() to the specified unit names and hence can handle weird characters nicely and will add unit suffixes as necessary.
2012-10-16man: Fix typo in udevadm documentationFerenc Wágner
2012-10-16Reword sentences that contain psuedo-English "resp."Andrew Eikum
As you likely know, Arch Linux is in the process of moving to systemd. So I was reading through the various systemd docs and quickly became baffled by this new abbreviation "resp.", which I've never seen before in my English-mother-tongue life. Some quick Googling turned up a reference: <http://www.transblawg.eu/index.php?/archives/870-Resp.-and-other-non-existent-English-wordsNicht-existente-englische-Woerter.html> I guess it's a literal translation of the German "Beziehungsweise", but English doesn't work the same way. The word "respectively" is used exclusively to provide an ordering connection between two lists. E.g. "the prefixes k, M, and G refer to kilo-, mega-, and giga-, respectively." It is also never abbreviated to "resp." So the sentence "Sets the default output resp. error output for all services and sockets" makes no sense to a natural English speaker. This patch removes all instances of "resp." in the man pages and replaces them with sentences which are much more clear and, hopefully, grammatically valid. In almost all instances, it was simply replacing "resp." with "or," which the original author (Lennart?) could probably just do in the future. The only other instances of "resp." are in the src/ subtree, which I don't feel privileged to correct. Signed-off-by: Andrew Eikum <aeikum@codeweavers.com>