Can I mask the systemd-journal-flush service and run journalctl --flush later manually? On my archlinux installation, I realised that flushing the journal logs to disk by the systemd-journal-flush service significantly prolongs the boot process and masking the service improves boot time. Can I permanently mask the service and run `journalctl --flush` later when the computer is idle to flush the journal logs to disk. Will this cause any undesirable system behaviour?

Others point out that running journald without any persistent logs, is an option. This approach is documented without any particular warnings, _and_ is used on large numbers of systems. Fedora started with no persistent journal plus a syslog daemon, and Debian still defaults that way.

So there's no reason to expect a problem.

I would feel free to mask the original service, and arrange for the flush to be run later however you like.

If at some later point you have a weird system crash during the boot process, you might want to re-enable it (and set a low `SyncIntervalSec=` in journald.conf), to try and recover any relevant log messages.