Searched refs:follow (Results 1 – 25 of 36) sorted by relevance
12
| /systemd-251/src/journal-remote/ |
| D | journal-gatewayd.c | 64 bool follow; member
183 if (m->follow) { in request_reader_entries()
241 if (m->tmp == NULL && m->follow) in request_reader_entries()
375 m->follow = true; in request_parse_arguments_iterator()
385 m->follow = r; in request_parse_arguments_iterator()
|
| D | journal-upload.h | 72 bool follow);
|
| D | journal-upload-journal.c | 374 bool follow) { in open_journal_for_upload() argument
381 if (follow) { in open_journal_for_upload()
|
| /systemd-251/src/basic/ |
| D | stat-util.c | 38 int is_dir(const char* path, bool follow) { in is_dir() argument
44 if (follow) in is_dir()
|
| D | stat-util.h | 16 int is_dir(const char *path, bool follow);
|
| /systemd-251/shell-completion/zsh/ |
| D | _journalctl | 98 {-f,--follow}'[Follow journal]' \
101 '--no-tail[Show all lines, even in follow mode]' \
|
| D | _resolvectl | 82 '--cname=no[Do not follow CNAME redirects]' \
|
| /systemd-251/test/units/ |
| D | testsuite-04.sh | 142 journalctl --follow --file=/var/log/journal/*/* | head -n1 || [[ $? -eq 1 ]]
|
| /systemd-251/docs/ |
| D | DISTRO_PORTING.md | 12 You need to make the follow changes to adapt systemd to your
|
| D | CODE_QUALITY.md | 64 ensure that editors follow the right indentiation styles automatically.
|
| D | INITRD_INTERFACE.md | 40 * Storage daemons run from the initrd should follow the guide on
|
| D | DESKTOP_ENVIRONMENTS.md | 54 * Application units should follow the scheme `app[-<launcher>]-<ApplicationID>[@<RANDOM>].service`
|
| D | GROUP_RECORD.md | 28 they follow the same GECOS syntax requirements as `realName`.
|
| D | BLOCK_DEVICE_LOCKING.md | 67 Note that the file locks follow the usual access semantics of BSD locks: since
|
| D | HACKING.md | 14 Please make sure to follow our [Coding Style](CODING_STYLE.md) when submitting
166 If you find a bug that impacts the security of systemd, please follow the
|
| D | CONTRIBUTING.md | 10 We welcome contributions from everyone. However, please follow the following guidelines when postin…
|
| D | PASSWORD_AGENTS.md | 19 It is easy to write additional agents. The basic algorithm to follow looks like this:
|
| D | JOURNAL_EXPORT_FORMATS.md | 20 * Two journal entries that follow each other are separated by a double newline.
|
| D | BOOT_LOADER_INTERFACE.md | 112 recommended to follow the following rules when picking identifiers for the
|
| D | ENVIRONMENT.md | 185 fashion. Note that by default only boot loader entries which follow the
206 specified udev's `net_id` builtin will follow the specified naming scheme
|
| D | CODING_STYLE.md | 97 - If you define (non-flags) enums, follow this template:
535 using it unless they can also follow the program's choice. Moreover, in
|
| D | CGROUP_DELEGATION.md | 71 though it's a good thing to follow it then too. Rule #2 is not enforced on
342 can entirely generically follow the single rule that you just use the cgroup
|
| /systemd-251/ |
| D | README.md | 37 When preparing patches for systemd, please follow our [Coding Style Guidelines](docs/CODING_STYLE.m…
|
| D | TODO | 77 * rework mount.c and swap.c to follow proper state enumeration/deserialization
1315 * seems that when we follow symlinks to units we prefer the symlink
1453 - follow PropertiesChanged state more closely, to deal with quick logouts and
1480 …- check if we can make journalctl by default use --follow mode inside of less if called without ar…
1816 should not follow symlinks. None of the other adjustment or creation
1817 calls follow symlinks.
|
| /systemd-251/shell-completion/bash/ |
| D | journalctl | 41 --disk-usage -f --follow --header
|
12