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

[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 (ulrich.wi...@rz.uni‑regensburg.de)
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 status=1
>> systemd[1]: Failed to start NIS/YP Clients to NIS Domain Binder.
>> systemd[1]: ypbind.service: Unit entered failed state.
>> systemd[1]: ypbind.service: Failed with result 'exit‑code'.
>> systemd[1]: Reached target User and Group Name Lookups.
>>
>> The interesting point is that ypbind.service is disabled. So why is 
> ypbind‑systemd‑pre complaining about NIS domain not being set?
> 
> Maybe ypbind‑systemd‑pre.service has Wants= or Requires= on
> ybind.service?

Neither, sorry. Or at least I could not find such.

# systemctl status ypbind-systemd-pre
● ypbind-systemd-pre.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)
# systemctl status ypbind
● ypbind.service - NIS/YP Clients to NIS Domain Binder
   Loaded: loaded (/usr/lib/systemd/system/ypbind.service; disabled; vendor
preset: disabled)
   Active: inactive (dead)
 Docs: man:ypbind(8)

BTW: Is it a bug that "systemctl show no-such-service" does not signal any
error (besides maybe ``LoadError=org.freedesktop.DBus.Error.FileNotFound "No
such file or directory"'')?

> 
> Either way, this sounds like something to talk to your distro/package
> of ypbind with.
> 
> Lennart
> 
> ‑‑
> Lennart Poettering, Berlin



___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

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

[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-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.service: Unit entered failed state.
>> systemd[1]: ypbind.service: Failed with result 'exit-code'.
>> systemd[1]: Reached target User and Group Name Lookups.
>> 
>> The interesting point is that ypbind.service is disabled. So why is 
> ypbind-systemd-pre complaining about NIS domain not being set?
>> 
> 
> And how exactly ypbind-systemd-pre is related to ypbind.service?

Actually I don't know, but does it make any sense to start it if NIS is not
being used?

> 
>> (systemd-228-157.9.1.x86_64)
>> 
>> Regards,
>> Ulrich
>> 
>> 
>> 
>> ___
>> systemd-devel mailing list
>> systemd-devel@lists.freedesktop.org 
>> https://lists.freedesktop.org/mailman/listinfo/systemd-devel 
>> 
> 
> ___
> systemd-devel mailing list
> systemd-devel@lists.freedesktop.org 
> https://lists.freedesktop.org/mailman/listinfo/systemd-devel 



___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

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

[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 issues I've found this one
 very similar to what I
see.

Here's What I have and what I was able to troubleshoot until now:

> I'm facing this  issue on Fedora 32.
> I'm also trying to boot freeswitch service on a nspawn container (CentOS
> 7) with the following settings, see bellow:
>
> [Service]
> Type=forking
> EnvironmentFile=/etc/sysconfig/freeswitch
> PIDFile=/var/run/freeswitch/freeswitch.pid
> ExecStart=/opt/freeswitch/bin/freeswitch -ncwait -nonat -nonatmap -rp
> WorkingDirectory=/var/run/freeswitch
> User=freeswitch
> Group=freeswitch
> PermissionsStartOnly=true
> TimeoutSec=45s
> Restart=always
> LimitCORE=infinity
> LimitNOFILE=10
> LimitNPROC=6
> #LimitSTACK=240
> LimitRTPRIO=infinity
> LimitRTTIME=700*IOSchedulingClass=realtime
> IOSchedulingPriority=2
> CPUSchedulingPolicy=rr
> CPUSchedulingPriority=89*
> UMask=0007
>
> The only way to make freeswitch run is by removing the IOScheduling and
> CPUScheduling options.
> If they are set freeswitch won't start giving:
>
> Failed at step SETSCHEDULER spawning /opt/freeswitch/bin/freeswitch:
> Operation not permitted
> and/or
> Failed at step IOPRIO spawning /opt/freeswitch/bin/freeswitch: Operation
> not permitted
>
> I've noticed that if I give the same CPUScheduling options to the
> 'systemd-nspawn@'.service service on the Fedora 32 hosting
> system I don't have the following error anymore in the container:
> Failed at step SETSCHEDULER spawning /opt/freeswitch/bin/freeswitch:
> Operation not permitted
>
> The only error that remains is the:
>
> Failed at step IOPRIO spawning /opt/freeswitch/bin/freeswitch: Operation
> not permitted
>
What is the best way to have this options set the right way and make
everything work as expected inside the nspawn container?

Cheers,

--

*Nuno Miguel Reis* | *Unified Communication** Systems*
M. +351 913907481 | nr...@wavecom.pt
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Mount in volatile mode

[Lennart Poettering]

On Mi, 27.05.20 08:10, Emmanuel Garette (egare...@cadoles.com) 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-systemd.before=systemd-volatile-root.service in the relevant
/etc/fstab lines. That way the mount is established before s-v-r.s
runs. Isn't that all you need?

I think what you are seeing is a bug though, we should order this
automatically like that. If so, can you file an issue on github about
this?

Lennart

--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

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

[Lennart Poettering]

On Do, 28.05.20 15:43, Ulrich Windl (ulrich.wi...@rz.uni-regensburg.de) 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 status=1
> systemd[1]: Failed to start NIS/YP Clients to NIS Domain Binder.
> systemd[1]: ypbind.service: Unit entered failed state.
> systemd[1]: ypbind.service: Failed with result 'exit-code'.
> systemd[1]: Reached target User and Group Name Lookups.
>
> The interesting point is that ypbind.service is disabled. So why is 
> ypbind-systemd-pre complaining about NIS domain not being set?

Maybe ypbind-systemd-pre.service has Wants= or Requires= on
ybind.service?

Either way, this sounds like something to talk to your distro/package
of ypbind with.

Lennart

--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

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

[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/YP Clients to NIS Domain Binder.
> systemd[1]: ypbind.service: Unit entered failed state.
> systemd[1]: ypbind.service: Failed with result 'exit-code'.
> systemd[1]: Reached target User and Group Name Lookups.
> 
> The interesting point is that ypbind.service is disabled. So why is 
> ypbind-systemd-pre complaining about NIS domain not being set?
> 

And how exactly ypbind-systemd-pre is related to ypbind.service?

> (systemd-228-157.9.1.x86_64)
> 
> Regards,
> Ulrich
> 
> 
> 
> ___
> systemd-devel mailing list
> systemd-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/systemd-devel
> 

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

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

[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.service: Unit entered failed state.
systemd[1]: ypbind.service: Failed with result 'exit-code'.
systemd[1]: Reached target User and Group Name Lookups.

The interesting point is that ypbind.service is disabled. So why is 
ypbind-systemd-pre complaining about NIS domain not being set?

(systemd-228-157.9.1.x86_64)

Regards,
Ulrich



___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

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

[Gavin]

thanks for your reply !


my system is ubuntu 18.0.4?? and the version of systemd I am compiling is 
systemd-245.




-- Original --
From: "systemd-devel-request"https://lists.freedesktop.org/mailman/listinfo/systemd-devel
or, via email, send a message with subject or body 'help' to
systemd-devel-requ...@lists.freedesktop.org

You can reach the person managing the list at
systemd-devel-ow...@lists.freedesktop.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of systemd-devel digest..."


Today's Topics:

   1. Re:  Some issues about compiling systemd on linux (Dave 
Howorth)
   2.  Some issues about compiling systemd on linux
  (=?gb18030?B?R2F2aW4=?=)
   3. Re:  Some issues about compiling systemd 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:03 +
From: Fredrik Hugosson https://lists.freedesktop.org/archives/systemd-devel/attachments/20200528/980286cd/attachment.htm>;
-- next part --
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 124955 bytes
Desc: image001.png
URL: 
<https://lists.freedesktop.org/archives/systemd-devel/attachments/20200528/980286cd/attachment.png>;

--

Subject: Digest Footer

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel


--

End of systemd-devel Digest, Vol 121, Issue 40
**___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

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

[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 been unable to solve this problem.



../src/libsystemd/sd-bus/test-bus-vtable-cc.cc:1:1: error: ??test?? does not 
name a type
 test-bus-vtable.c
 ^~~~
[1272/1466] Compiling C object 
'test-dhcp-optio...xe/src_libsystemd-network_test-dhcp-option.c.o'
ninja: build stopped: subcommand failed.
Makefile:2: recipe for target 'all' failed
make: *** [all] Error 1


How can I solve this problem?


My ultimate goal is to run the journald module on ARM. I can transplant the 
systemd. Of course, it is better to be able to compile the journald 
separately. But I don't know how to cross-compile systemd yet, can you 
give me some help?
   


I look forward to receiving your reply??


Best Regards??___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

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

[Dave Howorth]

On Thu, 28 May 2020 17:35:05 +0800
"黄桂丰" <670915...@qq.com> 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 systemd, but I
> encountered many problems during the compilation process, and now I
> have been unable to solve this problem.      
> 
> 
>     How can I solve this problem?
> 
>     My ultimate goal is to run the journald module on ARM.
> I can transplant the systemd. Of course, it is better to be able to
> compile the journald separately. But I don't know how to
> cross-compile systemd yet, can you give me some help?    
> 
>     I look forward to receiving your reply！

You don't say what distro you are using (or where else you got linux)
nor what version of systemd you are using. 

journald and journalctl etc are normally included with systemd. They
are for example with Raspbian, which is an ARM version of Debian.

> Best Regards！
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel