[systemd-devel] systemd-modules-load path

where is the systemd-modules-load.service to load the .ko file path ? http://www.freedesktop.org/software/systemd/man/modules-load.d.html this example doesn't tell us where is the virtio-net.ko file.___ systemd-devel mailing list

Re: [systemd-devel] runlevel target semantic doubt

On Tue, Oct 27, 2015 at 10:27 AM, kennedy wrote: > runlevel*.target for compatibility with sysV, just a symbol link to > systemd's target ? > > means that users can use runlevel*.target instead of default.target to > setting boot sequence ? > Any target unit can be used as

[systemd-devel] runlevel target semantic doubt

runlevel*.target for compatibility with sysV, just a symbol link to systemd's target ? means that users can use runlevel*.target instead of default.target to setting boot sequence ? quote:

Re: [systemd-devel] SMACK runtime vs build-time checks? (aka: tmp.mount broke my boot)

On Sun, Oct 18, 2015 at 12:22:15PM +0200, Kay Sievers wrote: > On Sun, Oct 18, 2015 at 6:01 AM, Mantas Mikulėnas wrote: > > So far all existing SELinux and SMACK options had runtime checks – if > > systemd was built with +SMACK but the kernel wasn't, it still worked fine. > >

Re: [systemd-devel] How to source a variable file using systemd

On Tue, Oct 27, 2015 at 04:05:18PM +0530, Soumya Koduri wrote: > EnvironmentFile=/etc/myconfig > > ExecStart=/bin/bash -c 'source ${MY_ENV_FILE} && echo ${MY_ENV_VAR}' Systemd also does shell-like variable substitution, so potentially it's decided to interpolate in the value of $MY_ENV_VAR

Re: [systemd-devel] systemd-modules-load path

On Tue, Oct 27, 2015 at 10:12 AM, kennedy wrote: > where is the systemd-modules-load.service to load the .ko file path ? > > http://www.freedesktop.org/software/systemd/man/modules-load.d.html > > this example doesn't tell us where is the virtio-net.ko file. > modules-load.d

[systemd-devel] How to source a variable file using systemd

Hi, We have a use-case where in we have to read an environment variable (say ${MY_ENV_FILE}) from a file (say /etc/myconfig) and source ${MY_ENV_FILE} to read yet another environment variable (say ${MY_ENV_VAR} in our systemd service file. I first tried out below --

Re: [systemd-devel] How to source a variable file using systemd

On Tue, Oct 27, 2015 at 12:35 PM, Soumya Koduri wrote: > Hi, > > We have a use-case where in we have to read an environment variable (say > ${MY_ENV_FILE}) from a file (say /etc/myconfig) and source ${MY_ENV_FILE} > to read yet another environment variable (say ${MY_ENV_VAR}

Re: [systemd-devel] How to source a variable file using systemd

On Tue, 27.10.15 16:05, Soumya Koduri (skod...@redhat.com) wrote: > Hi, > > We have a use-case where in we have to read an environment variable (say > ${MY_ENV_FILE}) from a file (say /etc/myconfig) and source ${MY_ENV_FILE} to > read yet another environment variable (say ${MY_ENV_VAR} in our

Re: [systemd-devel] How to source a variable file using systemd

Thanks Richard & Mantas. That did the trick. -Soumya On 10/27/2015 04:11 PM, Richard Maw wrote: On Tue, Oct 27, 2015 at 04:05:18PM +0530, Soumya Koduri wrote: EnvironmentFile=/etc/myconfig ExecStart=/bin/bash -c 'source ${MY_ENV_FILE} && echo ${MY_ENV_VAR}' Systemd also does

Re: [systemd-devel] Proper way of installing avahi dbus activation file

Am 27.10.2015 um 19:42 schrieb Pacho Ramos: El lun, 26-10-2015 a las 22:06 +0100, Reindl Harald escribió: [...] by the Also/Alias in the install section of proper units like the Fedora ones [root@srv-rhsoft:~]$ cat /usr/lib/systemd/system/avahi-daemon.service [Unit] Description=Avahi

Re: [systemd-devel] SMACK runtime vs build-time checks? (aka: tmp.mount broke my boot)

On Tue, 27.10.15 10:35, Karel Zak (k...@redhat.com) wrote: > On Sun, Oct 18, 2015 at 12:22:15PM +0200, Kay Sievers wrote: > > On Sun, Oct 18, 2015 at 6:01 AM, Mantas Mikulėnas wrote: > > > So far all existing SELinux and SMACK options had runtime checks – if > > > systemd was

[systemd-devel] Why are some of my units starting later than others?

Hello. Systemd 219 here on an embedded target (yocto build). I'm looking at the bootchart output and seeing some units that are WantedBy multi-user.target that are starting much later than others. There are no other requires on these service units so I'm not sure why one would start 4 seconds