We're currently running systemd-212. man doesn't seem to cover this.
--bind=, --bind-ro=
Bind mount a file or directory from the host into the
container. Either takes a path argument -- in which case the specified
path will be mounted from the host to the same path in the cont
On 09.06.2014 09:33, Leho Kraav wrote:
After upgrading systemd 208 -> 212, every single cron job creates this
flood in systemd journal:
juuni 09 09:20:01 xps14 crond[15112]: pam_unix(crond:session): session
opened for user root by (uid=0)
juuni 09 09:20:01 xps14 systemd[15113]: pam_unix(syst
On 10.06.2014 19:01, Lennart Poettering wrote:
In the meantime mgilbert's suggestion for using EDIT **loginctl enable-linger**
command seems to accomplish the goal of quieting cron logging. Any
side effects to consider?
Well, you keep the systemd user instance running all the time then
instead
On 10.06.2014 13:20, Lennart Poettering wrote:
On Mon, 09.06.14 09:33, Leho Kraav (l...@kraav.com) wrote:
After upgrading systemd 208 -> 212, every single cron job creates
this flood in systemd journal:
Can I quiet this down somehow?
The idea with the journal is that we log everyth
On 09.06.2014 10:43, Reindl Harald wrote:
nobody cares because the developers point of view is that what is
interesting for them needs to be also faced by the sysadmin
otherwise this would be only logged in debug-mode and bugreports
not closed: https://bugzilla.redhat.com/show_bug.cgi?id=1072368
After upgrading systemd 208 -> 212, every single cron job creates this
flood in systemd journal:
juuni 09 09:20:01 xps14 crond[15112]: pam_unix(crond:session): session
opened for user root by (uid=0)
juuni 09 09:20:01 xps14 systemd[15113]: pam_unix(systemd-user:session):
session opened for use
On 22.05.2014 03:03, Lennart Poettering wrote:
What is "pf"?
http://pf.natalenko.name
Please try upstream kernels. If you run patched kernels, and they work
differently than upstream kernels, then please contct the maintianers of
those patched kernels. Thanks.
You were right here, thanks f
Hi all
I've been trying to solve this for several hours over multiple days now
and am at the end of my wits, so asking for help.
One machine, my laptop, boots "systemd-nspawn -D /srv/canister -b"
perfectly fine. All services load OK in a blink of an eye, login prompt
appears, all is good. E
