From 4160043a0fac8b812905b7502ce34adf3af538f1 Mon Sep 17 00:00:00 2001 From: Luke Shumaker Date: Tue, 6 Sep 2016 02:27:18 -0400 Subject: move man pages to appropriate directories --- man/systemd-journal-remote.xml | 325 ----------------------------------------- 1 file changed, 325 deletions(-) delete mode 100644 man/systemd-journal-remote.xml (limited to 'man/systemd-journal-remote.xml') diff --git a/man/systemd-journal-remote.xml b/man/systemd-journal-remote.xml deleted file mode 100644 index 3899f175d4..0000000000 --- a/man/systemd-journal-remote.xml +++ /dev/null @@ -1,325 +0,0 @@ - - - - - - - - - systemd-journal-remote - systemd - - - - Developer - Zbigniew - Jędrzejewski-Szmek - zbyszek@in.waw.pl - - - - - - systemd-journal-remote - 8 - - - - systemd-journal-remote - Receive journal messages over the network - - - - - systemd-journal-remote - OPTIONS - -o/--output=DIR|FILE - SOURCES - - - - - Description - - - systemd-journal-remote is a command to - receive serialized journal events and store them to the journal. - Input streams are in the - - Journal Export Format - , - i.e. like the output from - journalctl --output=export. For transport over - the network, this serialized stream is usually carried over an - HTTPS connection. - - - - - Sources - - - Sources can be either "active" - (systemd-journal-remote requests and pulls - the data), or "passive" - (systemd-journal-remote waits for a - connection and then receives events pushed by the other side). - - - - systemd-journal-remote can read more than one - event stream at a time. They will be interleaved in the output - file. In case of "active" connections, each "source" is one - stream, and in case of "passive" connections, each connection can - result in a separate stream. Sockets can be configured in - "accept" mode (i.e. only one connection), or "listen" mode (i.e. - multiple connections, each resulting in a stream). - - - - When there are no more connections, and no more can be created - (there are no listening sockets), then - systemd-journal-remote will exit. - - - Active sources can be specified in the following - ways: - - - - When is given as a - positional argument, events will be read from standard input. - Other positional arguments will be treated as filenames - to open and read from. - - - - - - With the - option, - events will be retrieved using HTTP from - ADDRESS. This URL should refer to the - root of a remote - systemd-journal-gatewayd8 - instance (e.g. http://some.host:19531/ or - https://some.host:19531/). - - - - Passive sources can be specified in the following - ways: - - - - - - ADDRESS must be an - address suitable for (cf. - systemd.socket5). - systemd-journal-remote will listen on this - socket for connections. Each connection is expected to be a - stream of journal events. - - - - - - - - ADDRESS must be - either a negative integer, in which case it will be - interpreted as the (negated) file descriptor number, or an - address suitable for (c.f. - systemd.socket5). - In the first case, matching file descriptor must be inherited - through - $LISTEN_FDS/$LISTEN_PID. - In the second case, an HTTP or HTTPS server will be spawned on - this port, respectively for and - . Currently, only POST requests - to /upload with Content-Type: - application/vnd.fdo.journal are supported. - - - - - $LISTEN_FDS - - systemd-journal-remote - supports the - $LISTEN_FDS/$LISTEN_PID - protocol. Open sockets inherited through socket activation - behave like those opened with - described above, unless they are specified as an argument in - - or - - above. In the latter case, an HTTP or HTTPS server will be - spawned using this descriptor and connections must be made - over the HTTP protocol. - - - - - - - - Sinks - - The location of the output journal can be specified - with or . For "active" - sources, this option is required. - - - - - - - Will write to this journal file. The filename - must end with .journal. The file will be - created if it does not exist. If necessary (journal file full, - or corrupted), the file will be renamed following normal - journald rules and a new journal file will be created in its - stead. - - - - - - Will create journal files underneath directory - DIR. The directory must exist. If - necessary (journal files over size, or corrupted), journal - files will be rotated following normal journald rules. Names - of files underneath DIR will be - generated using the rules described below. - - - - If is not used, the output - directory /var/log/journal/remote/ will be - used. In case the output file is not specified, journal files - will be created underneath the selected directory. Files will be - called - remote-hostname.journal, - where the hostname part is the - escaped hostname of the source endpoint of the connection, or the - numerical address if the hostname cannot be determined. - - In case of "active" sources, the output file name must - always be given explicitly. - - - - Options - - The following options are understood: - - - - - - One of none or - host. For the first, only one output - journal file is used. For the latter, a separate output file - is used, based on the hostname of the other endpoint of a - connection. - - In case of "active" sources, the output file name must - always be given explicitly and only none - is allowed. - - - - - - - Compress or not, respectively, the data in the - journal using XZ. - - - - - - - Periodically sign or not, respectively, the - data in the journal using Forward Secure Sealing. - - - - - - - Program to invoke to retrieve data. The journal - event stream must be generated on standard output. - - Examples: - - --getter='curl "-HAccept: application/vnd.fdo.journal" https://some.host:19531/' - - --getter='wget --header="Accept: application/vnd.fdo.journal" -O- https://some.host:19531/' - - - - - - - - - - Examples - Copy local journal events to a different journal directory: - -journalctl -o export | systemd-journal-remote -o /tmp/dir - - - - - Retrieve all available events from a remote - systemd-journal-gatewayd8 - instance and store them in - /var/log/journal/remote/remote-some.host.journal: - -systemd-journal-remote --url http://some.host:19531/ - - - - Retrieve current boot events and wait for new events from a remote - systemd-journal-gatewayd8 - instance, and store them in - /var/log/journal/remote/remote-some.host.journal: - -systemd-journal-remote --url http://some.host:19531/entries?boot&follow - - - - - - See Also - - systemd-journal-upload8, - journalctl1, - systemd-journald.service8, - systemd-journal-gatewayd.service8 - journal-remote.conf5 - - - -- cgit v1.2.3-54-g00ecf