Re: [systemd-devel] character limit by using "/run/systemd/journal/syslog"
On Mi, 18.04.18 16:12, Stanislav Kopp (stask...@gmail.com) wrote: > HI all, > > I'm not sure if it's systemd/journald issue, but maybe you can help > me. We're logging apache error logs with "logger" so we can write them > to specific file using rsyslog, if I run "logger" without any options > - all are duplicated in journald and I can see them in "journalctl" > overview what is no needed, I can tell "logger" to write to > "/run/systemd/journal/syslog" directly and then I don't see them in > journalctl but the logs are trimmed (about 437 characters what is > strange number). So I don't understand if it's a "logger" bug or > somehow related to journald or even rsyslog. This way you bypass systemd-journald entirely, and any such line breaks are between logger and rsyslog. This also means we can't really help you with this. Please ping the util-linux and rsyslog folks about this. Thanks. Lennart -- Lennart Poettering, Red Hat ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] character limit by using "/run/systemd/journal/syslog"
HI all, I'm not sure if it's systemd/journald issue, but maybe you can help me. We're logging apache error logs with "logger" so we can write them to specific file using rsyslog, if I run "logger" without any options - all are duplicated in journald and I can see them in "journalctl" overview what is no needed, I can tell "logger" to write to "/run/systemd/journal/syslog" directly and then I don't see them in journalctl but the logs are trimmed (about 437 characters what is strange number). So I don't understand if it's a "logger" bug or somehow related to journald or even rsyslog. Full option from apache config. ErrorLog "| /usr/bin/logger -p local1.info --socket /run/systemd/journal/syslog" Best, Stan ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Run fuse in nspawn container?
On Di, 10.04.18 13:34, Johannes Ernst (johannes.er...@gmail.com) wrote: > I’m running with > > systemd-nspawn —capability=all > > but now I also need /dev/fuse and I’m not permitted to create it. > > man systemd-nspawn says that "Device nodes may not be created.” which sounds > like game over and no Fuse in the container. Is it? Yeah, we don't allow arbitrary device node creation in nspawn containers by default, as that's not safe. You may use --bind=/dev/fuse, but ymmv as fuse isn't properly virtualized for container environments last time I looked. Lennart -- Lennart Poettering, Red Hat ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
