summaryrefslogtreecommitdiff
path: root/man/systemd.time.xml
Commit message (Collapse)AuthorAgeFilesLines
* man: small fixes to systemd.time Calendar EventsChristopher Gurnee2023-05-051-2/+2
|
* tree-wide: replace "plural(s)" by "plurals"Zbigniew Jędrzejewski-Szmek2022-10-171-3/+2
| | | | | | | | (s) is just ugly with a vibe of DOS. In most cases just using the normal plural form is more natural and gramatically correct. There are some log_debug() statements left, and texts in foreign licenses or headers. Those are not touched on purpose.
* license: LGPL-2.1+ -> LGPL-2.1-or-laterYu Watanabe2020-11-091-1/+1
|
* man: extend on the usec/sec discrepancyLennart Poettering2020-08-281-0/+10
| | | | | | | | | | | | | | | Let's document the discrepancy between the Sec and USec suffixing of unit files and D-Bus properties at three places: in "systemctl show" (where it already was briefly mentioned), in the D-Bus interface description (at one place at least, i.e. the most prominent of properties that encapsulate time values, there are many more) and in the general man page explaining time values. By documenting this at all three places I think we now do as much as we can do about this highlighting the discrepancy of the naming and the reasons behind it. Fixes: #2047
* tree-wide: fixes for assorted grammar and spelling issuesZbigniew Jędrzejewski-Szmek2020-07-061-13/+15
| | | | Fixes #16363. Also includes some changes where I generalized the pattern.
* man: expand on the star…end/repetition time expressionsLennart Poettering2020-05-051-9/+8
| | | | | | | And attempt to explain what is requested in #15030, but still be concise. Fixes: #15030
* tree-wide: fix how we set $TZLennart Poettering2019-11-131-3/+2
| | | | | According to tzset(3) we need to prefix timezone names with ":". Let's do so hence, to avoid any ambiguities and follow documented behaviour.
* analyze: add 'timestamp' verbZbigniew Jędrzejewski-Szmek2019-05-171-0/+4
| | | | | | | | | We had 'calendar' and 'timespan', but the third one was missing. Also consistently order the verbs as calendar/timestamp/timespan in help. The output from 'timespan' is highlighted more. Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1711065.
* man: use same header for all filesZbigniew Jędrzejewski-Szmek2019-03-141-1/+1
| | | | | | | The "include" files had type "book" for some raeason. I don't think this is meaningful. Let's just use the same everywhere. $ perl -i -0pe 's^..DOCTYPE (book|refentry) PUBLIC "-//OASIS//DTD DocBook XML V4.[25]//EN"\s+"http^<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"\n "http^gms' man/*.xml
* man: standarize on one-line license headerZbigniew Jędrzejewski-Szmek2019-03-141-4/+1
| | | | | | No need to waste space, and uniformity is good. $ perl -i -0pe 's|\n+<!--\s*SPDX-License-Identifier: LGPL-2.1..\s*-->|\n<!-- SPDX-License-Identifier: LGPL-2.1+ -->|gms' man/*.xml
* analyze: Add "timespan" command to dump time span in usecChris Down2018-10-231-0/+4
| | | | | | | | | | | | | | | | | | | | | | This is useful for a couple of cases, I'm mostly interested in case #1: 1. Verifying "reasonable" values in a trivially scriptable way 2. Debugging unexpected time span parsing directly Test Plan: ``` % build/systemd-analyze timespan 20 Original: 20 μs: 20 Human: 20us % build/systemd-analyze timespan 20ms Original: 20ms μs: 20000 Human: 20ms % build/systemd-analyze timespan 20z Failed to parse time span '20z': Invalid argument ```
* man: mention µsLennart Poettering2018-10-171-1/+1
|
* man: drop unused <authorgroup> tags from man sourcesZbigniew Jędrzejewski-Szmek2018-06-141-9/+0
| | | | | | | | | | | | Docbook styles required those to be present, even though the templates that we use did not show those names anywhere. But something changed semi-recently (I would suspect docbook templates, but there was only a minor version bump in recent years, and the changelog does not suggest anything related), and builds now work without those entries. Let's drop this dead weight. Tested with F26-F29, debian unstable. $ perl -i -0pe 's/\s*<authorgroup>.*<.authorgroup>//gms' man/*xml
* tree-wide: remove Lennart's copyright linesLennart Poettering2018-06-141-2/+0
| | | | | | | | | | | These lines are generally out-of-date, incomplete and unnecessary. With SPDX and git repository much more accurate and fine grained information about licensing and authorship is available, hence let's drop the per-file copyright notice. Of course, removing copyright lines of others is problematic, hence this commit only removes my own lines and leaves all others untouched. It might be nicer if sooner or later those could go away too, making git the only and accurate source of authorship information.
* tree-wide: drop 'This file is part of systemd' blurbLennart Poettering2018-06-141-2/+0
| | | | | | | | | | | | | | | | This part of the copyright blurb stems from the GPL use recommendations: https://www.gnu.org/licenses/gpl-howto.en.html The concept appears to originate in times where version control was per file, instead of per tree, and was a way to glue the files together. Ultimately, we nowadays don't live in that world anymore, and this information is entirely useless anyway, as people are very welcome to copy these files into any projects they like, and they shouldn't have to change bits that are part of our copyright header for that. hence, let's just get rid of this old cruft, and shorten our codebase a bit.
* tree-wide: drop license boilerplateZbigniew Jędrzejewski-Szmek2018-04-061-13/+0
| | | | | | | | | | Files which are installed as-is (any .service and other unit files, .conf files, .policy files, etc), are left as is. My assumption is that SPDX identifiers are not yet that well known, so it's better to retain the extended header to avoid any doubt. I also kept any copyright lines. We can probably remove them, but it'd nice to obtain explicit acks from all involved authors before doing that.
* analyze: add new "calendar" commandLennart Poettering2017-11-201-1/+6
| | | | | | | This little new command can parse, validate, normalize calendar events, and calculate when they will elapse next. This should be useful for anyone writing calendar events and who'd like to validate the expression before running them as timer units.
* Add SPDX license identifiers to man pagesZbigniew Jędrzejewski-Szmek2017-11-191-0/+2
|
* Added docs for new timezone support added at #6788 (#6865)Ivan Kurnosov2017-09-191-21/+27
|
* man: improve readability of time shorthands and their normalized forms. (#5912)Mark Stosberg2017-05-081-17/+11
|
* calendarspec: allow repetition values with rangesDouglas Christman2016-12-161-4/+5
| | | | | "Every other hour from 9 until 5" can be written as `9..17/2:00` instead of `9,11,13,15,17:00`
* calendarspec: make specifications with ranges reversibleDouglas Christman2016-11-241-2/+2
| | | | "*-*-01..03" is now formatted as "*-*-01..03" instead of "*-*-01,02,03"
* calendarspec: add support for scheduling timers at the end of the monthDouglas Christman2016-11-231-0/+5
| | | | | | | | "*-*~1" => The last day of every month "*-02~3..5" => The third, fourth, and fifth last days in February "Mon 05~07/1" => The last Monday in May Resolves #3861
* util-lib: make timestamp generation and parsing reversible (#3869)Lennart Poettering2016-08-031-78/+72
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch improves parsing and generation of timestamps and calendar specifications in two ways: - The week day is now always printed in the abbreviated English form, instead of the locale's setting. This makes sure we can always parse the week day again, even if the locale is changed. Given that we don't follow locale settings for printing timestamps in any other way either (for example, we always use 24h syntax in order to make uniform parsing possible), it only makes sense to also stick to a generic, non-localized form for the timestamp, too. - When parsing a timestamp, the local timezone (in its DST or non-DST name) may be specified, in addition to "UTC". Other timezones are still not supported however (not because we wouldn't want to, but mostly because libc offers no nice API for that). In itself this brings no new features, however it ensures that any locally formatted timestamp's timezone is also parsable again. These two changes ensure that the output of format_timestamp() may always be passed to parse_timestamp() and results in the original input. The related flavours for usec/UTC also work accordingly. Calendar specifications are extended in a similar way. The man page is updated accordingly, in particular this removes the claim that timestamps systemd prints wouldn't be parsable by systemd. They are now. The man page previously showed invalid timestamps as examples. This has been removed, as the man page shouldn't be a unit test, where such negative examples would be useful. The man page also no longer mentions the names of internal functions, such as format_timestamp_us() or UNIX error codes such as EINVAL.
* man: improve wording for calendar spec's repetition values (#3687)Ivan Shapovalov2016-07-081-1/+1
|
* calendarspec: use ".." notation for ranges of weekdaysDouglas Christman2016-07-011-5/+5
| | | | | For backwards compatibility, both the new format (Mon..Wed) and the old format (Mon-Wed) are supported.
* calendarspec: allow ranges in date and time specificationsDouglas Christman2016-07-011-1/+4
| | | | Resolves #3042
* man: calendarspec sub-second supportHristo Venev2015-11-171-0/+5
|
* man: document our definition of a year and a monthLennart Poettering2015-11-131-2/+2
| | | | Let's be accurate here, as this might be surprising to people.
* util-lib: when parsing time values, accept "M" as short for "month"Lennart Poettering2015-11-131-1/+1
| | | | | | | | nginx defines an uppercase "M" that way (in contrast to the lowercase "m" for "minute"), and it sounds like an OK logic to follow, so that we understand a true superset of time values nginx understands. http://nginx.org/en/docs/syntax.html
* doc: correct orthography, word forms and missing/extraneous wordsJan Engelhardt2015-11-061-1/+1
|
* doc: correct punctuation and improve typography in documentationJan Engelhardt2015-11-061-6/+6
|
* man: fix systemd.time RAS syndrome and line lengthHristo Venev2015-10-251-6/+6
| | | | "UTC time" is a RAP phrase (redundant acronym phrase phrase).
* man: mention UTC support for calendar eventsHristo Venev2015-10-151-21/+24
|
* man: mention UTC support for timestampsHristo Venev2015-10-151-17/+25
|
* man: Remove instances of pseudo-English "resp."Andrew Eikum2015-06-291-1/+1
| | | | | | | Me again :) Just noticed one of these in a manpage and did another pass to clean them up. See 16dad32e437fdf2ffca03cc60a083d84bd31886f for explanation, though the link needs updating: <http://transblawg.eu/2004/02/26/resp-and-other-non-existent-english-wordsnicht-existente-englische-worter/>
* man: revert dynamic paths for split-usr setupsTom Gundersen2015-06-181-4/+1
| | | | | | | | | | | | | | | | | | | | | | | This did not really work out as we had hoped. Trying to do this upstream introduced several problems that probably makes it better suited as a downstream patch after all. At any rate, it is not releaseable in the current state, so we at least need to revert this before the release. * by adjusting the path to binaries, but not do the same thing to the search path we end up with inconsistent man-pages. Adjusting the search path too would be quite messy, and it is not at all obvious that this is worth the effort, but at any rate it would have to be done before we could ship this. * this means that distributed man-pages does not make sense as they depend on config options, and for better or worse we are still distributing man pages, so that is something that definitely needs sorting out before we could ship with this patch. * we have long held that split-usr is only minimally supported in order to boot, and something we hope will eventually go away. So before we start adding even more magic/effort in order to make this work nicely, we should probably question if it makes sense at all.
* man: generate configured paths in manpagesFilipe Brandenburger2015-05-281-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In particular, use /lib/systemd instead of /usr/lib/systemd in distributions like Debian which still have not adopted a /usr merge setup. Use XML entities from man/custom-entities.ent to replace configured paths while doing XSLT processing of the original XML files. There was precedent of some files (such as systemd.generator.xml) which were already using this approach. This addresses most of the (manual) fixes from this patch: http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/tree/debian/patches/Fix-paths-in-man-pages.patch?h=experimental-220 The idea of using generic XML entities was presented here: http://lists.freedesktop.org/archives/systemd-devel/2015-May/032240.html This patch solves almost all the issues, with the exception of: - Path to /bin/mount and /bin/umount. - Generic statements about preference of /lib over /etc. These will be handled separately by follow up patches. Tested: - With default configure settings, ran "make install" to two separate directories and compared the output to confirm they matched exactly. - Used a set of configure flags including $CONFFLAGS from Debian: http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/tree/debian/rules Installed the tree and confirmed the paths use /lib/systemd instead of /usr/lib/systemd and that no other unexpected differences exist. - Confirmed that `make distcheck` still passes.
* Reindent man pages to 2chZbigniew Jędrzejewski-Szmek2015-02-031-269/+256
|
* man: Clarify effect when both calendar day and date are listed in timerChris Atkinson2015-01-011-2/+2
| | | | | | | See bug 87859 (https://bugs.freedesktop.org/show_bug.cgi?id=87859). Bug reporter found the language describing the effect of specifying both a day and date unclear; hopefully the attached patch will clarify and allow the bug to be closed.
* calendarspec: parse 'quarterly' and 'semi-annually' as shortcutsLennart Poettering2014-10-271-5/+8
|
* man: document what "minutely" now meansLennart Poettering2014-10-271-0/+2
|
* man: document yearly and annually in systemd.time(7)Zbigniew Jędrzejewski-Szmek2014-07-161-6/+12
| | | | https://bugs.freedesktop.org/show_bug.cgi?id=81158
* time: support @ syntax for denoting times since the UNIX epoch 1970-1-1Lennart Poettering2014-03-251-5/+11
|
* man: typo fixThomas Hindoe Paaboel Andersen2014-01-041-1/+1
|
* man: wording and grammar updatesJan Engelhardt2013-09-121-2/+2
| | | | | | | | | | | | 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)
* man: wording and grammar updatesJan Engelhardt2013-09-101-1/+1
| | | | | | | | | 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)
* man: add more formatting markupZbigniew Jędrzejewski-Szmek2013-07-021-11/+12
|
* man: improve grammar and word formatting in numerous man pagesJason St. John2013-07-021-31/+31
| | | | | | | | | | Use proper grammar, word usage, adjective hyphenation, commas, capitalization, spelling, etc. To improve readability, some run-on sentences or sentence fragments were revised. [zj: remove the space from 'file name', 'host name', and 'time zone'.]
* man: time - exchange some 'colons' with 'commas'Tom Gundersen2013-01-301-2/+2
|
View Lorry Controller Status