On 09/18/2012 12:11 PM, Per Jessen wrote:

Andreas Jaeger wrote:

...

On 09/16/2012 11:37 AM, Christofer C. Bell wrote:

...

On Sun, Sep 16, 2012 at 3:22 AM, Per Jessen wrote:

...

Thanks - I'm surprised there is no way of disabling it when it brings me absolutely nothing that I want (the current situation). In openSUSE I think we should have omitted /var/log/journal, but it is easily deleted of course.

Without it, systemd has no way to log anything. If you're going to get rid of journald, you may consider booting your system with sysvinit (deprecated) and eschewing systemd entirely (which you won't be able to do for much longer).

systemd should work without the journal,

systemd seems to be hell-bent on world domination, the journal is taking over for syslog. At least we don't need to let it consume any diskspace. The question is - how does one appropriately remove "/var/log/journal"? See bnc#780624 for what happened when I tried "rm -Rf /var/log/journal".

does the following command not working to ditch journald systemctl mask systemd-journal.service Togan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

El 18/09/12 07:11, Per Jessen escribió:

systemd seems to be hell-bent on world domination,

Yes, it is an evil plot to move linux forward into the 21 century, with modern, OS specific tools. the journal is taking

over for syslog. At least we don't need to let it consume any diskspace. The question is - how does one appropriately remove "/var/log/journal"? See bnc#780624 for what happened when I tried "rm -Rf /var/log/journal".

The bug you mention has absolutely nothing to do with journald... "WARNING: at /home/abuild/rpmbuild/BUILD/kernel-default-3.4.6/linux-3.4/fs/inode.c:280 drop_nlink+0x2f/0x40()" wrong choir ;-) that is something for kernel developers to check ! . -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Tue, Sep 18, 2012 at 5:11 AM, Per Jessen wrote:

systemd seems to be hell-bent on world domination, the journal is taking over for syslog. At least we don't need to let it consume any diskspace. The question is - how does one appropriately remove "/var/log/journal"? See bnc#780624 for what happened when I tried "rm -Rf /var/log/journal".

On my system, which has been running for several months, /var/log takes up a total of 65M. Are you working in the embedded world where space is really at a premium? I can guarantee that if you're not, you'll derive more space savings out of rebuilding every package to exclude those binaries you never actually use. For example, let's look at all the binaries in coreutils: /bin/arch /bin/basename /bin/cat /bin/chgrp /bin/chmod /bin/chown /bin/cp /bin/date /bin/dd /bin/df /bin/echo /bin/false /bin/kill /bin/ln /bin/ls /bin/md5sum /bin/mkdir /bin/mknod /bin/mktemp /bin/mv /bin/pwd /bin/readlink /bin/rm /bin/rmdir /bin/sleep /bin/sort /bin/stat /bin/stty /bin/su /bin/sync /bin/touch /bin/true /bin/uname /usr/bin/[ /usr/bin/arch /usr/bin/base64 /usr/bin/basename /usr/bin/cat /usr/bin/chcon /usr/bin/chgrp /usr/bin/chmod /usr/bin/chown /usr/bin/chroot /usr/bin/cksum /usr/bin/comm /usr/bin/cp /usr/bin/csplit /usr/bin/cut /usr/bin/date /usr/bin/dd /usr/bin/df /usr/bin/dir /usr/bin/dircolors /usr/bin/dirname /usr/bin/du /usr/bin/echo /usr/bin/env /usr/bin/expand /usr/bin/expr /usr/bin/factor /usr/bin/false /usr/bin/fmt /usr/bin/fold /usr/bin/groups /usr/bin/head /usr/bin/hostid /usr/bin/id /usr/bin/install /usr/bin/join /usr/bin/kill /usr/bin/link /usr/bin/ln /usr/bin/logname /usr/bin/ls /usr/bin/md5sum /usr/bin/mkdir /usr/bin/mkfifo /usr/bin/mknod /usr/bin/mktemp /usr/bin/mv /usr/bin/nice /usr/bin/nl /usr/bin/nohup /usr/bin/nproc /usr/bin/od /usr/bin/paste /usr/bin/pathchk /usr/bin/pinky /usr/bin/pr /usr/bin/printenv /usr/bin/printf /usr/bin/ptx /usr/bin/pwd /usr/bin/readlink /usr/bin/realpath /usr/bin/rm /usr/bin/rmdir /usr/bin/runcon /usr/bin/seq /usr/bin/sha1sum /usr/bin/sha224sum /usr/bin/sha256sum /usr/bin/sha384sum /usr/bin/sha512sum /usr/bin/shred /usr/bin/shuf /usr/bin/sleep /usr/bin/sort /usr/bin/split /usr/bin/stat /usr/bin/stdbuf /usr/bin/stty /usr/bin/su /usr/bin/sum /usr/bin/sync /usr/bin/tac /usr/bin/tail /usr/bin/tee /usr/bin/test /usr/bin/timeout /usr/bin/touch /usr/bin/tr /usr/bin/true /usr/bin/truncate /usr/bin/tsort /usr/bin/tty /usr/bin/uname /usr/bin/unexpand /usr/bin/uniq /usr/bin/unlink /usr/bin/uptime /usr/bin/users /usr/bin/vdir /usr/bin/wc /usr/bin/who /usr/bin/whoami /usr/bin/yes How many of these do you actually ever use, perhaps a third of them? Multiple that by thousands of packages and you'll realize a lot more space savings (in the order of gigabytes) over deleting /var/log/journal. -- Chris -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org