Hi, Russell Stuart: > Well you won't if you don't work on device where the > overheads of storing it twice hurt. If they do you don't have much > choice. You can turn off syslog, but not journald. > You can, however, tell journald to not store anything anywhere. "Storage=None" in journald.conf. Or, if you'd prefer to not drop early boot messages on the floor, you can use a small amount of volatile storage.
If the pass through an additional process is too much overhead for your syslogging, then I'd respectfully suggest that you have *way* worse problems than any percieved lock-in. > Journald it an excellent starting point for a discussion on lock in. Nobody prevents you from writing a replacement; it's not hard to figure out what systemd does to pass the relevant file descriptors along. Or you could extend rsyslog so that it can act as a drop-in. You'd lose systemctl's ability to show you the last few lines of program output, but that feature appears not to be important to you anyway. FWIW, this is the exact opposite of any reasonable meaning of "lock-in" that I can come up with. > After all why are we forced to use a binary logging just because > You seem to have sent this email before you finished writing it. In any case, you are not. -- -- Matthias Urlichs -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150121165802.ga4...@smurf.noris.de
