[systemd-devel] Antw: [EXT] Re: Q: ypbind-systemd-pre[1756]: \nError: NIS domain not specified.\n

2020-05-28 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 28.05.2020 um 22:25 in Nachricht <24474_1590697505_5ED01E21_24474_24_1_20200528202504.GA118706@gardel-login>: > On Do, 28.05.20 15:43, Ulrich Windl ([email protected]‑regensburg.de) wrote: > >> Hi! >> >> Monitoring the messages created when booting SLES12 SP5,

[systemd-devel] Antw: [EXT] Re: Q: ypbind-systemd-pre[1756]: \nError: NIS domain not specified.\n

2020-05-28 Thread Ulrich Windl
>>> Andrei Borzenkov schrieb am 28.05.2020 um 17:41 in Nachricht <17498_1590680482_5ECFDBA2_17498_482_1_09c71a67-5db5-a767-386d-249cb37674ac@gmai .com>: > 28.05.2020 16:43, Ulrich Windl пишет: >> Hi! >> >> Monitoring the messages created when booting SLES12 SP5, I noticed these: >> >> ypbind-sys

[systemd-devel] systemd-nspawn: Failed at step SETSCHEDULER spawning /opt/freeswitch/bin/freeswitch: Operation not permitted

2020-05-28 Thread Nuno Reis
Hi guys. I'm new to this mailling list so I hope this is a good place to ask this type of stuff. I'm trying to have a nspawn container to run freeswitch with some realtime settings set at service level and I'm facing some permission issues as I explain bellow. When trying to search for related is

Re: [systemd-devel] Mount in volatile mode

2020-05-28 Thread Lennart Poettering
On Mi, 27.05.20 08:10, Emmanuel Garette ([email protected]) wrote: > > With volatile mode enable (systemd.volatile=yes), it's different. > /etc/fstab file is copied too late by systemd.tmpfiles. Hmm, not sure I grok everything right what you are saying, but I figure you should be able to add x

Re: [systemd-devel] Q: ypbind-systemd-pre[1756]: \nError: NIS domain not specified.\n

2020-05-28 Thread Lennart Poettering
On Do, 28.05.20 15:43, Ulrich Windl ([email protected]) wrote: > Hi! > > Monitoring the messages created when booting SLES12 SP5, I noticed these: > > ypbind-systemd-pre[1756]: \nError: NIS domain not specified.\n > systemd[1]: ypbind.service: Control process exited, code=exited st

Re: [systemd-devel] Q: ypbind-systemd-pre[1756]: \nError: NIS domain not specified.\n

2020-05-28 Thread Andrei Borzenkov
28.05.2020 16:43, Ulrich Windl пишет: > Hi! > > Monitoring the messages created when booting SLES12 SP5, I noticed these: > > ypbind-systemd-pre[1756]: \nError: NIS domain not specified.\n > systemd[1]: ypbind.service: Control process exited, code=exited status=1 > systemd[1]: Failed to start NIS

[systemd-devel] Q: ypbind-systemd-pre[1756]: \nError: NIS domain not specified.\n

2020-05-28 Thread Ulrich Windl
Hi! Monitoring the messages created when booting SLES12 SP5, I noticed these: ypbind-systemd-pre[1756]: \nError: NIS domain not specified.\n systemd[1]: ypbind.service: Control process exited, code=exited status=1 systemd[1]: Failed to start NIS/YP Clients to NIS Domain Binder. systemd[1]: ypbind

Re: [systemd-devel] systemd-devel Digest, Vol 121, Issue 40

2020-05-28 Thread Gavin
md on linux   (Fredrik Hugosson) -- Message: 1 Date: Thu, 28 May 2020 11:19:19 +0100 From: Dave Howorth https://lists.freedesktop.org/archives/systemd-devel/attachments/20200528/7091cde1/attachment-0001.htm>; -- Message: 3 Date: Thu, 28 May 2020 11:17

[systemd-devel] Some issues about compiling systemd on linux

2020-05-28 Thread Gavin
Hello , I have a project that needs to use the journald module in systemd. My initial idea was to compile journald separately, but then I found that this would not work. So I started to try to compile systemd, but I encountered many problems during the compilation process, and now I have bee

Re: [systemd-devel] Some issues about compiling systemd on linux

2020-05-28 Thread Dave Howorth
On Thu, 28 May 2020 17:35:05 +0800 "黄桂丰" <[email protected]> wrote: > Hello , > >      I have a project that needs to use the journald > module in systemd. My initial idea was to compile journald > separately, but then I found that this would not work. > >      So I started to try to compile syste