History log of /systemd/units/systemd-journal-catalog-update.service.in
Revision Date Author Comments Expand
75f709fbf284041d951717cfb3bf6304db0fa7c9 02-Feb-2015 Lennart Poettering <lennart@poettering.net>

units: so far we defaulted to 90s as default timeout for most things, let's do so for our oneshot services too Fewer surprises, and stuff...

0775b9b61120f8be99cd45a7df907b828188cb47 01-Feb-2015 Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>

units: set TimeoutSec on some oneshot services Services which are not crucial to system bootup, and have Type=oneshot can effectively "hang" the system if they fail to complete for whatever reason. To allow the boot to continue, kill them after a timeout. In case of systemd-journal-flush the flush will continue in the background, and in the other two cases the job will be aborted, but this should not result in any permanent problem.

d6bc8348d5be8576a475ac8ced2b0146e60fb71f 25-Sep-2014 Daniel Buch <boogiewasthere@gmail.com>

readahead: wipe out readahead

/systemd/Makefile-man.am /systemd/Makefile.am /systemd/configure.ac /systemd/man/sd-daemon.xml /systemd/man/sd-login.xml /systemd/man/sd-readahead.xml /systemd/man/sd_readahead.xml /systemd/man/systemd-notify.xml /systemd/man/systemd-readahead-replay.service.xml /systemd/po/POTFILES.skip /systemd/shell-completion/zsh/_systemd /systemd/src/cryptsetup/cryptsetup-generator.c /systemd/src/gpt-auto-generator/gpt-auto-generator.c /systemd/src/notify/notify.c /systemd/src/readahead/Makefile /systemd/src/readahead/readahead-analyze.c /systemd/src/readahead/readahead-collect.c /systemd/src/readahead/readahead-common.c /systemd/src/readahead/readahead-common.h /systemd/src/readahead/readahead-replay.c /systemd/src/readahead/readahead.c /systemd/src/readahead/sd-readahead.c /systemd/src/readahead/test-ssd.c /systemd/src/systemd/sd-readahead.h /systemd/system-preset/90-systemd.preset .gitignore ldconfig.service quotaon.service.in system-update.target systemd-backlight@.service.in systemd-binfmt.service.in systemd-firstboot.service.in systemd-fsck-root.service.in systemd-fsck@.service.in systemd-journal-catalog-update.service.in systemd-modules-load.service.in systemd-quotacheck.service.in systemd-random-seed.service.in systemd-readahead-collect.service.in systemd-readahead-done.service.in systemd-readahead-done.timer systemd-readahead-drop.service systemd-readahead-replay.service.in systemd-remount-fs.service.in systemd-rfkill@.service.in systemd-sysctl.service.in systemd-sysusers.service.in systemd-tmpfiles-clean.service.in systemd-tmpfiles-setup-dev.service.in systemd-tmpfiles-setup.service.in systemd-udev-hwdb-update.service.in systemd-update-done.service.in systemd-update-utmp.service.in systemd-vconsole-setup.service.in
b63bb8a724cab7a315f04c3068f0d628cc163b8b 16-Jun-2014 Lennart Poettering <lennart@poettering.net>

units: drop RefuseManualStart= from a couple of update services The only update service we really need to guard like this is systemd-tmpfiles-setup.service since if invoked manually might create /var/run/nologin and thus blocking the user from login. The other services are pretty much idempotent and don't suffer by this problem, hence let's simplify them.

ecde7065f7b11a7a226d2f7b0e90e998a6347a59 13-Jun-2014 Lennart Poettering <lennart@poettering.net>

units: rebuild /etc/passwd, the udev hwdb and the journal catalog files on boot Only when necessary of course, nicely guarded with the new ConditionNeedsUpdate= condition we added.