Re: [CentOS] systemd does not generate both StandardOutput and StandardError files in /var/log/ directory

On Fri, Nov 5, 2021 at 2:16 PM Simon Matter wrote: > Hi, > > > Hi, > > > > I am running CentOS Linux release 7.9.2009 (Core). I have created a > > systemd > > service for a java service. I want to capture both stdout and stderr to > > files under /var/log directory. > > # cat /etc/redhat-release

Re: [CentOS] systemd does not generate both StandardOutput and StandardError files in /var/log/ directory

Hi, > Hi, > > I am running CentOS Linux release 7.9.2009 (Core). I have created a > systemd > service for a java service. I want to capture both stdout and stderr to > files under /var/log directory. > # cat /etc/redhat-release > CentOS Linux release 7.9.2009 (Core) > # > # rpm -qa | grep systemd

[CentOS] systemd does not generate both StandardOutput and StandardError files in /var/log/ directory

Hi, I am running CentOS Linux release 7.9.2009 (Core). I have created a systemd service for a java service. I want to capture both stdout and stderr to files under /var/log directory. # cat /etc/redhat-release CentOS Linux release 7.9.2009 (Core) # # rpm -qa | grep systemd

Re: [CentOS] systemd | Requires statement with an instantiated service

--On Wednesday, September 01, 2021 6:36 PM +0200 Leon Fauster via CentOS wrote: How to apply a "Requires" with an instantiated service. Example: a@.service b.service a@.service is started as a@host1.service and b.service must be started after a@host1.service but the unit will be

[CentOS] systemd | Requires statement with an instantiated service

Maybe the work day is already to long. I can not find a solution for following requirement. How to apply a "Requires" with an instantiated service. Example: a@.service b.service a@.service is started as a@host1.service and b.service must be started after a@host1.service but the unit will be

[CentOS] systemd alias for SMTP provider (and other services supplied by alternative providers)

I just finished adding a custom service to send an email on system shutdown/startup: I ended up coding an After for postfix.service on CentOS 8 so the mail would get delivered before the system shut down. (I think I might need a delay, too, to allow

Re: [CentOS] systemd and 'Stale file handle' errors?

Jonathan Billings wrote: > So, the chronyd systemd unit looks like this: > > # /usr/lib/systemd/system/chronyd.service > [Unit] > Description=NTP client/server > Documentation=man:chronyd(8) man:chrony.conf(5) > After=ntpdate.service sntp.service ntpd.service >

Re: [CentOS] systemd and 'Stale file handle' errors?

On Thu, May 13, 2021 at 02:15:15PM +, James Pearson wrote: > > I have a CentOS 7 system where I needed to restart chronyd - but the > systemctl restart failed with the error: > > systemd[1]: Starting NTP client/server... > systemd[43578]: Failed at step NAMESPACE spawning

Re: [CentOS] systemd and 'Stale file handle' errors?

> I have a CentOS 7 system where I needed to restart chronyd - but the > systemctl restart failed with the error: > > systemd[1]: Starting NTP client/server... > systemd[43578]: Failed at step NAMESPACE spawning /usr/sbin/chronyd: > Stale file handle > systemd[1]: chronyd.service: control

[CentOS] systemd and 'Stale file handle' errors?

I have a CentOS 7 system where I needed to restart chronyd - but the systemctl restart failed with the error: systemd[1]: Starting NTP client/server... systemd[43578]: Failed at step NAMESPACE spawning /usr/sbin/chronyd: Stale file handle systemd[1]: chronyd.service: control process exited,

Re: [CentOS] systemd / services / current process list

Am 06.11.20 um 14:57 schrieb Leon Fauster: Hi, following requirement is needed here (forced by application migration from C6->C8): I have two services running under supervision by systemd. ServiceA: runs as user AppUser ServiceB: runs as user AppUser ServiceB can see "all" processes from

[CentOS] systemd / services / current process list

Hi, following requirement is needed here (forced by application migration from C6->C8): I have two services running under supervision by systemd. ServiceA: runs as user AppUser ServiceB: runs as user AppUser ServiceB can see "all" processes from AppUser (ps aux) running by systemd (in fact it

Re: [CentOS] Systemd service unit file needs to wait until a specific interface is up

On 24/09/2020 16:28, Simon Matter wrote: On 24/09/2020 13:41, Simon Matter wrote: I've been dealing with issues like this for a while - systems with multiple interfaces, some of which do not come up for quite a while, and I need to wait for all to be up before running certain tasks. Still

Re: [CentOS] Systemd service unit file needs to wait until a specific interface is up

> On 24/09/2020 13:41, Simon Matter wrote: >>> I've been dealing with issues like this for a while - systems with multiple interfaces, some of which do not come up for quite a while, and I need to wait for all to be up before running certain tasks. Still haven't found

Re: [CentOS] Systemd service unit file needs to wait until a specific interface is up

On 24/09/2020 13:41, Simon Matter wrote: I've been dealing with issues like this for a while - systems with multiple interfaces, some of which do not come up for quite a while, and I need to wait for all to be up before running certain tasks. Still haven't found anything very satisfactory.

Re: [CentOS] Systemd service unit file needs to wait until a specific interface is up

> On Wed, 23 Sep 2020 at 23:39, Orion Poplawski wrote: > >> On 9/23/20 7:07 AM, Stephen John Smoogen wrote: >> > On Wed, 23 Sep 2020 at 04:33, Carlos Lopez wrote: >> > >> >> Hi all, >> >> >> >> >> >> With SystemD, how can I make certain service dependent on certain >> network >> >> interfaces

Re: [CentOS] Systemd service unit file needs to wait until a specific interface is up

On Wed, 23 Sep 2020 at 23:39, Orion Poplawski wrote: > On 9/23/20 7:07 AM, Stephen John Smoogen wrote: > > On Wed, 23 Sep 2020 at 04:33, Carlos Lopez wrote: > > > >> Hi all, > >> > >> > >> With SystemD, how can I make certain service dependent on certain > network > >> interfaces being up? > >>

Re: [CentOS] Systemd service unit file needs to wait until a specific interface is up

On 9/23/20 7:07 AM, Stephen John Smoogen wrote: On Wed, 23 Sep 2020 at 04:33, Carlos Lopez wrote: Hi all, With SystemD, how can I make certain service dependent on certain network interfaces being up? For example, I have an 802.1ad bond interface I need to wait on for being up (this

Re: [CentOS] Systemd service unit file needs to wait until a specific interface is up

Perfect!! Many thanks Stephen. Works like a charm. On 23/09/2020, 15:08, "CentOS on behalf of Stephen John Smoogen" wrote: On Wed, 23 Sep 2020 at 04:33, Carlos Lopez wrote: > Hi all, > > > With SystemD, how can I make certain service dependent on certain network >

Re: [CentOS] Systemd service unit file needs to wait until a specific interface is up

On Wed, 23 Sep 2020 at 04:33, Carlos Lopez wrote: > Hi all, > > > With SystemD, how can I make certain service dependent on certain network > interfaces being up? > > For example, I have an 802.1ad bond interface I need to wait on for being > up (this interface has no ip address assigned, it is

Re: [CentOS] Systemd service unit file needs to wait until a specific interface is up

In article <004e8170-e842-4e8b-9623-db3ea236d...@outlook.com>, Carlos Lopez wrote: > Hi all, > > > With SystemD, how can I make certain service dependent on certain network > interfaces being up? > > For example, I have an 802.1ad bond interface I need to wait on for being up > (this

[CentOS] Systemd service unit file needs to wait until a specific interface is up

Hi all, With SystemD, how can I make certain service dependent on certain network interfaces being up? For example, I have an 802.1ad bond interface I need to wait on for being up (this interface has no ip address assigned, it is used to capture networks packets with a tcpdump’s script).

Re: [CentOS] systemd syslog.target

GMT+00:00) > To: CentOS mailing list > Subject: Re: [CentOS] systemd syslog.target > > Hi,>> I've noticed that there are several systemd unit files in > CentOS 7 and 8> with the optionAfter=syslog.targetin the [Unit] > section, but since systemd> version 198 syslog.tar

Re: [CentOS] systemd syslog.target

CentOS Date: 31/07/2020 10:02 (GMT+00:00) To: CentOS mailing list Subject: Re: [CentOS] systemd syslog.target Hi,>> I've noticed that there are several systemd unit files in CentOS 7 and 8> with the optionAfter=syslog.targetin the [Unit] section, but since systemd>

Re: [CentOS] systemd syslog.target

Hi, > > I've noticed that there are several systemd unit files in CentOS 7 and 8 > with the optionAfter=syslog.targetin the [Unit] section, but since systemd > version 198 syslog.target has not existed.I deduce from this that > "After=syslog.target" is ignored by systemd and can therefore be

[CentOS] systemd syslog.target

I've noticed that there are several systemd unit files in CentOS 7 and 8 with the optionAfter=syslog.targetin the [Unit] section, but since systemd version 198 syslog.target has not existed.I deduce from this that "After=syslog.target" is ignored by systemd and can therefore be removed.

Re: [CentOS] systemd environment var composed of vars

Am 06.07.20 um 17:25 schrieb Leon Fauster: Is it somehow possible to use composed ENV vars in a systemd unit file? Simple example, env file has ADDRESS=foo PORT=bar LISTEN=${ADDRESS}:${PORT} putting ${ADDRESS}:${PORT} directly in the unit file works, $LISTEN not. Does systemd supports such

[CentOS] systemd environment var composed of vars

Is it somehow possible to use composed ENV vars in a systemd unit file? Simple example, env file has ADDRESS=foo PORT=bar LISTEN=${ADDRESS}:${PORT} putting ${ADDRESS}:${PORT} directly in the unit file works, $LISTEN not. Does systemd supports such var substitution? -- Leon

Re: [CentOS] systemd-coredump service

I do have both those files. But I was under the wrong assumption that there is a systemd service for the same as mentioned here . Thanks for the clarification. Now how do I enable systemd to generate core files? I

Re: [CentOS] systemd-coredump service

> I am unable to locate systemd-coredump service on CentOS 7.5. It is not > listed under "systemctl -a" and also I'm unable to locate the associated > unit file (folder /usr/lib/systemd/system/ ). Am I missing any package > which installs this service? I don't really understand what you are

[CentOS] systemd-coredump service

I am unable to locate systemd-coredump service on CentOS 7.5. It is not listed under "systemctl -a" and also I'm unable to locate the associated unit file (folder /usr/lib/systemd/system/ ). Am I missing any package which installs this service? ___

Re: [CentOS] systemd: Failed unmounting /var on reboot, should I worry about fs corruption?

Thanks, after reading some more complaints online and suggestions on this, I think setting up a lazy umount of /var is the best option until the bug is resolved in Centos 8. The lazy umount prevents systemd from registering and reporting the error that ordinary umount /var would generate (such

Re: [CentOS] systemd: Failed unmounting /var on reboot, should I worry about fs corruption?

In article , Ján Lalinský wrote: > Hi all, > > I have Centos 8 installed on a physical machine (www6) with separate LVM > volumes for /, /var, /var/lib/mysql etc. > > System boot proceeds without a hiccup, in terminal systemctl status says > everything is OK and running, journalctl says so as

[CentOS] systemd: Failed unmounting /var on reboot, should I worry about fs corruption?

Hi all, I have Centos 8 installed on a physical machine (www6) with separate LVM volumes for /, /var, /var/lib/mysql etc. System boot proceeds without a hiccup, in terminal systemctl status says everything is OK and running, journalctl says so as well - systemd mounts everything stated in fstab.

Re: [CentOS] systemd-sleep

Tate Belden wrote: > https://www.freedesktop.org/software/systemd/man/systemd-sleep.conf.html > > On Mon, Jun 17, 2019 at 9:44 AM mark wrote: > > >> I found that one of my users' workstation is, for some reason, running >> systemd-sleep. I cannot find, anywhere on the system. system-sleep.conf >>

Re: [CentOS] systemd-sleep

https://www.freedesktop.org/software/systemd/man/systemd-sleep.conf.html On Mon, Jun 17, 2019 at 9:44 AM mark wrote: > I found that one of my users' workstation is, for some reason, running > systemd-sleep. I cannot find, anywhere on the system. system-sleep.conf > (or systemd-sleep.conf), nor

[CentOS] systemd-sleep

I found that one of my users' workstation is, for some reason, running systemd-sleep. I cannot find, anywhere on the system. system-sleep.conf (or systemd-sleep.conf), nor do I find systemctl status system[d]-sleep. How can I turn this thing off, other than renaming

Re: [CentOS] Systemd, PHP-FPM, and /cgi-bin scripts

Am 26.04.2019 um 09:38 schrieb Markus Falb : > > On 24.04.19 17:40, Benjamin Smith wrote: >> On Wednesday, April 24, 2019 3:44:04 AM PDT Leon Fauster via CentOS wrote: Am 24.04.2019 um 08:37 schrieb Benjamin Smith : > ... So I wrote a /cgi-bin script that works, takes the input, and

Re: [CentOS] Systemd, PHP-FPM, and /cgi-bin scripts

On 24.04.19 17:40, Benjamin Smith wrote: > On Wednesday, April 24, 2019 3:44:04 AM PDT Leon Fauster via CentOS wrote: >>> Am 24.04.2019 um 08:37 schrieb Benjamin Smith : ... >>> So I wrote a /cgi-bin script that works, takes the input, and even runs >>> the ... >> >> Why not implementing this

Re: [CentOS] Systemd, PHP-FPM, and /cgi-bin scripts

See responses below. On Wednesday, April 24, 2019 6:13:51 AM PDT Jonathan Billings wrote: > On Tue, Apr 23, 2019 at 11:37:51PM -0700, Benjamin Smith wrote: > > But... php-fpm has its own "tmp" directory, something like /tmp/systemd- > > private-RANDOM-php-fpm.service-RANDOM/tmp that the cgi-bin

Re: [CentOS] Systemd, PHP-FPM, and /cgi-bin scripts

On Wednesday, April 24, 2019 3:44:04 AM PDT Leon Fauster via CentOS wrote: > > Am 24.04.2019 um 08:37 schrieb Benjamin Smith : > > > > CentOS 7 server and Fedora 29 dev workstation, both with PHP 7.2, Apache > > 2.4, php-fpm, all updated. > > > > I have a web-based app I've been developing for

Re: [CentOS] Systemd, PHP-FPM, and /cgi-bin scripts

On Tue, Apr 23, 2019 at 11:37:51PM -0700, Benjamin Smith wrote: > But... php-fpm has its own "tmp" directory, something like /tmp/systemd- > private-RANDOM-php-fpm.service-RANDOM/tmp that the cgi-bin has no access to. > To be able to populate $_FILES in a way compatible with the rest of the >

Re: [CentOS] Systemd, PHP-FPM, and /cgi-bin scripts

> Am 24.04.2019 um 08:37 schrieb Benjamin Smith : > > CentOS 7 server and Fedora 29 dev workstation, both with PHP 7.2, Apache 2.4, > php-fpm, all updated. > > I have a web-based app I've been developing for some time, and recently the > need to upload files of large size EG 1 GB or larger,

[CentOS] Systemd, PHP-FPM, and /cgi-bin scripts

CentOS 7 server and Fedora 29 dev workstation, both with PHP 7.2, Apache 2.4, php-fpm, all updated. I have a web-based app I've been developing for some time, and recently the need to upload files of large size EG 1 GB or larger, has come up. So I wrote a /cgi-bin script that works, takes

Re: [CentOS] systemd

Hi, for compiling Kernel Modules it might be worth looking at DKMS. DKMS is available through EPEL and is designed to compile Kernel Modules in an automated way when ever Kernel Updates are made. For more Informations on DKMS see [1, 2, 3]. best regards, Markus [1] https://github.com/dell/dkms

Re: [CentOS] systemd

Jerry Geis wrote: > > Hi All - I have a systemd service file to start my application. > > Part of my service file is: > [Service] > Type=forking > ExecStart=/path to start > ExecStop=/path to stop > RemainAfterExit=yes > > This works fine "normally". > > However - when I do a "yum update; and

[CentOS] systemd

Hi All - I have a systemd service file to start my application. Part of my service file is: [Service] Type=forking ExecStart=/path to start ExecStop=/path to stop RemainAfterExit=yes This works fine "normally". However - when I do a "yum update; and reboot" my script detects a kernel change

Re: [CentOS] systemd

On Wed, Jan 09, 2019 at 06:00:31PM +0100, Simon Matter via CentOS wrote: > Maybe things _could_ be done the right way with systemd, but it doesn't > happen because it quickly starts to be very complex and it's a lot of work > to do it for a complete distribution. It just doesn't happen - or at

Re: [CentOS] systemd

On 1/9/19 9:00 AM, Simon Matter via CentOS wrote: Maybe things_could_ be done the right way with systemd, but it doesn't happen because it quickly starts to be very complex and it's a lot of work to do it for a complete distribution. If you've looked at the sysv init script for postgresql,

Re: [CentOS] systemd

On Wed, Jan 09, 2019 at 12:04:29PM -0500, Steve Clark wrote: > Hmm... > I don't see that in the postgresql.service file - this is CentOS Linux > release 7.5.1804 (Core) > postgresql-server-9.2.24-1.el7_5.x86_64 > > from /usr/lib/systemd/system/postgresql.service > ... > [Service] > Type=forking

Re: [CentOS] systemd

On 1/9/19 11:00 AM, Simon Matter via CentOS wrote: On Wed, Jan 09, 2019 at 10:43:38AM -0500, Steve Clark wrote: I am trying to understand what After= means in a unit file. Does it mean after the specified target is up and operational or only that the target has been started? I have

Re: [CentOS] systemd

On 01/09/2019 11:36 AM, Jonathan Billings wrote: > On Wed, Jan 09, 2019 at 10:43:38AM -0500, Steve Clark wrote: >> I am trying to understand what After= means in a unit file. Does it >> mean after the specified target is up and operational or only that >> the target has been started? >> >> I have

Re: [CentOS] systemd

> On Wed, Jan 09, 2019 at 10:43:38AM -0500, Steve Clark wrote: >> I am trying to understand what After= means in a unit file. Does it >> mean after the specified target is up and operational or only that >> the target has been started? >> >> I have something that needs postgres but postgres needs

Re: [CentOS] systemd

On Wed, Jan 09, 2019 at 10:43:38AM -0500, Steve Clark wrote: > I am trying to understand what After= means in a unit file. Does it > mean after the specified target is up and operational or only that > the target has been started? > > I have something that needs postgres but postgres needs to be

[CentOS] systemd

Hi List, I am trying to understand what After= means in a unit file. Does it mean after the specified target is up and operational or only that the target has been started? I have something that needs postgres but postgres needs to be operational not just started. Sometimes it can take a bit

Re: [CentOS] systemd automount of cifs share hangs

On 10/26/2018 12:25 PM, mark wrote: Wait a minute: are you running IPv6? What we see is that if a system doesn't get its IPv6 address, NFSv4 goes preferentially for that, and if it has that, and looses it, it will*NOT* fall back to IPv4, but hangs. All my interfaces have a link local IPv6

Re: [CentOS] systemd automount of cifs share hangs

> > Wait a minute: are you running IPv6? What we see is that if a system > doesn't get its IPv6 address, NFSv4 goes preferentially for that, and if > it has that, and looses it, it will *NOT* fall back to IPv4, but hangs. > > Nope. My router does not do IPv6. From what I've heard, the Myricom

Re: [CentOS] systemd automount of cifs share hangs

Kenneth Porter wrote: > --On Friday, October 19, 2018 2:33 PM -0700 Elliott Balsley > wrote: > >> I don't have a solution, but I wanted to point out this same hang >> happened to me recently with a Myricom 10Gb card. Apparently Myricom >> drivers do not support CentOS 7 smb connections, although

Re: [CentOS] systemd automount of cifs share hangs

--On Friday, October 19, 2018 2:33 PM -0700 Elliott Balsley wrote: I don't have a solution, but I wanted to point out this same hang happened to me recently with a Myricom 10Gb card. Apparently Myricom drivers do not support CentOS 7 smb connections, although HTTP traffic works fine. I

Re: [CentOS] systemd automount of cifs share hangs

On 10/21/2018 1:12 PM, Young, Gregory wrote: I have never used the .automount file I have the .mount file configured for various SAMBA shares, and I simply issued "systemctl enable share-x-y-z.mount" to get them to mount on boot. After a power failure, I can't guarantee that the NAS

Re: [CentOS] systemd automount of cifs share hangs

oot. Greg -Original Message- From: CentOS On Behalf Of Kenneth Porter Sent: October 19, 2018 3:39 PM To: CentOS mailing list Subject: [CentOS] systemd automount of cifs share hangs Running latest CentOS 7.5. Since I found out about automount unit files I've had mixed results using them to mount s

Re: [CentOS] systemd automount of cifs share hangs

> > But if I start the automount unit and ls the mount point, the shell hangs > and eventually, a long time later (I haven't timed it, maybe an hour), I > eventually get a prompt again. Control-C won't interrupt it. I can still > ssh in and get another session so it's just the process that's

[CentOS] systemd automount of cifs share hangs

Running latest CentOS 7.5. Since I found out about automount unit files I've had mixed results using them to mount shares from my NAS. Lately they seem to hang if I touch the mount point, but I can start the mount unit without problems. I had it working months ago, so I'm thinking something

Re: [CentOS] systemd equivalent of xinetd 'only_from' and 'banner_fail' attributes

On Wed, 8 Aug 2018 12:59:09 + James Pearson wrote: > James Pearson wrote: > > > > I'm attempting to port an existing xinetd service from CentOS 6 to > > something equivalent with systemd for CentOS 7 > > > > The existing xinetd config uses the attributes 'only_from' to limit > >

Re: [CentOS] systemd equivalent of xinetd 'only_from' and 'banner_fail' attributes

James Pearson wrote: > > I'm attempting to port an existing xinetd service from CentOS 6 to > something equivalent with systemd for CentOS 7 > > The existing xinetd config uses the attributes 'only_from' to limit > connections from a limited set of remote hosts and 'banner_fail' to > print a

[CentOS] systemd equivalent of xinetd 'only_from' and 'banner_fail' attributes

I'm attempting to port an existing xinetd service from CentOS 6 to something equivalent with systemd for CentOS 7 The existing xinetd config uses the attributes 'only_from' to limit connections from a limited set of remote hosts and 'banner_fail' to print a suitable error message when access

Re: [CentOS] systemd-udevd not applying ATTR to block device at boot

I suppose it would help if I posted relevant version info (sorry about that...) CentOS Linux release 7.4.1708 (Core) @ 3.10.0-693.11.6.el7.x86_64 systemd-219-42.el7_4.4.x86_64 $ modinfo virtio_scsi filename: /lib/modules/3.10.0-693.11.6.el7.x86_64/kernel/drivers/scsi/virtio_scsi.ko.xz

[CentOS] systemd-udevd not applying ATTR to block device at boot

Hi everyone, I have a udev rule file that contains a singular rule: SUBSYSTEM=="block", ACTION=="add|change", ENV{ID_VENDOR}=="*Google*", ENV{DEVTYPE}=="disk", ATTR{queue/scheduler}:="noop" When I use a Google Cloud instance and boot it, things work as expected and /dev/sda (a persistent

Re: [CentOS] systemd-journald errors

On Sun, Oct 29, 2017 at 07:54:50AM +, C. L. Martinez wrote: > Hi all, > > I have 5 CentOS 7 virtual guests installed (all fully patched to latest > release) and i have the following error in all of them: > > systemd-journald[7779]: File >

[CentOS] systemd-journald errors

Hi all, I have 5 CentOS 7 virtual guests installed (all fully patched to latest release) and i have the following error in all of them: systemd-journald[7779]: File /run/log/journal/b4a41f4214ca44f898638301891a6f2e/system.journal corrupted or uncleanly shut down, renaming and replacing. ??

[CentOS] systemd - service restart another service... (how?)

... but only upon its own start/restart hi everyone would you know a trick? PartOf= does the whole lot, stops when stopped, so no. Here I need only re/start, everything else is ignored. many thanks, L. ___ CentOS mailing list CentOS@centos.org

Re: [CentOS] systemd-networkd issue

Sometimes we build kernels that need the minimal amount of functionality that we can get away with, the environment this system is in an environment that does not use, and won't use IPv6 for some time. systemd-networkd has some nice features for setting link speed, renaming interfaces etc, and so

Re: [CentOS] systemd-networkd issue

On 10/04/2017 01:40 PM, James Hogarth wrote: > Nope. And find /etc/systemd -name network gives zilch. Yes, systemd-networkd does store its configuration in /etc/systemd/network, but the directory isn't created by the RPM; you need to create it yourself. As noted, systemd-networkd is in the RHEL

Re: [CentOS] systemd-networkd issue

On 4 Oct 2017 6:51 pm, wrote: James Hogarth wrote: > On 4 Oct 2017 3:13 pm, "Kenneth Porter" wrote: > > On 10/3/2017 8:14 PM, Phil Manuel wrote: > >> systemd-networkd doesn't use those files at all. >> >> If you look at the appropriate ifcfg files eg >>

Re: [CentOS] systemd-networkd issue

James Hogarth wrote: > On 4 Oct 2017 3:13 pm, "Kenneth Porter" wrote: > > On 10/3/2017 8:14 PM, Phil Manuel wrote: > >> systemd-networkd doesn't use those files at all. >> >> If you look at the appropriate ifcfg files eg >> /etc/sysconfig/network-scripts/ifcfg-em1 do you

Re: [CentOS] systemd-networkd issue

On 4 Oct 2017 3:13 pm, "Kenneth Porter" wrote: On 10/3/2017 8:14 PM, Phil Manuel wrote: > systemd-networkd doesn't use those files at all. > > If you look at the appropriate ifcfg files eg > /etc/sysconfig/network-scripts/ifcfg-em1 do you see IPV6_FAILURE_FATAL=no > ? >

Re: [CentOS] systemd-networkd issue

On 10/3/2017 8:14 PM, Phil Manuel wrote: systemd-networkd doesn't use those files at all. If you look at the appropriate ifcfg files eg /etc/sysconfig/network-scripts/ifcfg-em1 do you see IPV6_FAILURE_FATAL=no ? Where does systemd-networkd store its settings, then?

Re: [CentOS] systemd-networkd issue

On 4 October 2017 at 07:20, Phil Perry wrote: > On 04/10/17 03:46, Phil Manuel wrote: > >> Hi, >> >> If I disable ipv6 via the kernel command line, ipv6.disable=1, then >> systemd-networkd fails to bring up any interfaces. >> >> Removing the option and networking works as

Re: [CentOS] systemd-networkd issue

On 04/10/17 03:46, Phil Manuel wrote: Hi, If I disable ipv6 via the kernel command line, ipv6.disable=1, then systemd-networkd fails to bring up any interfaces. Removing the option and networking works as expected. Phil. How are you controlling your network interfaces? I am using NM.

Re: [CentOS] systemd-networkd issue

That's ok the link was a good idea however, it doesn't fix the issue with disabling ipv6 at the kernel level, fails with the same output Regards On Wed, 4 Oct 2017 at 14:39 Clint Dilks wrote: > Okay sorry about that. > > No Idea if it will work in CentOS, but is it

Re: [CentOS] systemd-networkd issue

Okay sorry about that. No Idea if it will work in CentOS, but is it worth trying to turn off ipv6 for a single nic as as outlined at https://coreos.com/os/docs/latest/network-config-with-networkd.html ? On Wed, Oct 4, 2017 at 4:14 PM, Phil Manuel wrote: > Hi Clint, > >

Re: [CentOS] systemd-networkd issue

Hi Clint, systemd-networkd doesn't use those files at all. On Wed, 4 Oct 2017 at 13:55 Clint Dilks wrote: > On Wed, Oct 4, 2017 at 3:46 PM, Phil Manuel wrote: > > > Hi, > > > > If I disable ipv6 via the kernel command line, ipv6.disable=1, then >

Re: [CentOS] systemd-networkd issue

On Wed, Oct 4, 2017 at 3:46 PM, Phil Manuel wrote: > Hi, > > If I disable ipv6 via the kernel command line, ipv6.disable=1, then > systemd-networkd fails to bring up any interfaces. > > Removing the option and networking works as expected. > Hi, If you look at the appropriate

[CentOS] systemd-networkd issue

Hi, If I disable ipv6 via the kernel command line, ipv6.disable=1, then systemd-networkd fails to bring up any interfaces. Removing the option and networking works as expected. Phil. ___ CentOS mailing list CentOS@centos.org

Re: [CentOS] systemd services and Restart?

Matthew Miller wrote: > > I think it's a good idea. We just haven't had a push (either at > Red Hat internally or Fedora upstream) to go through and enable this > everywhere it makes sense. The guidelines do recommend it: > > https://fedoraproject.org/wiki/Packaging:Systemd#Automatic_restarting >

Re: [CentOS] systemd services and Restart?

On Wed, Jun 28, 2017 at 12:54:43PM +, James Pearson wrote: > However, I notice that this option is only used in a few OS provided > service unit files - and was wondering about the wisdom of adding this > capability to other daemons/services? (e.g. chronyd or ntpd, crond, > rpcbind, etc,

Re: [CentOS] systemd services and Restart?

the first console disconnect. - Original Message - From: "James Pearson" <jame...@moving-picture.com> To: "centos" <centos@centos.org> Sent: Wednesday, June 28, 2017 7:54:43 AM Subject: [CentOS] systemd services and Restart? I've been trying out the R

[CentOS] systemd services and Restart?

I've been trying out the Restart= option in some of my own systemd service unit files - which appears to work fine However, I notice that this option is only used in a few OS provided service unit files - and was wondering about the wisdom of adding this capability to other daemons/services?

Re: [CentOS] systemd order help?

On Tue, Jun 13, 2017 at 01:33:33PM +0100, James Hogarth wrote: > >> Depending on your setup, you many want to look at converting your > >> automatic mounts into systemd mounts, and depend on that directly, > >> rather than on the autofs service. [...] > But unless you need a complicated map

Re: [CentOS] systemd order help?

On 13 June 2017 at 13:27, Matthew Miller wrote: > On Tue, Jun 13, 2017 at 06:34:54AM +0100, James Hogarth wrote: >> Depending on your setup, you many want to look at converting your >> automatic mounts into systemd mounts, and depend on that directly, >> rather than on the

Re: [CentOS] systemd order help?

On Tue, Jun 13, 2017 at 06:34:54AM +0100, James Hogarth wrote: > Depending on your setup, you many want to look at converting your > automatic mounts into systemd mounts, and depend on that directly, > rather than on the autofs service. [...] > Just one little thing to note here that many don't

Re: [CentOS] systemd order help?

On 12 Jun 2017 17:03, "Matthew Miller" wrote: On Mon, Jun 12, 2017 at 03:47:46PM +, James Pearson wrote: > I'm guessing I could use something like: > > After=autofs.service > Before=graphical.target > > Is this correct? > > However, I would like to use the same systemd

Re: [CentOS] systemd order help?

Matthew Miller wrote: > > You probably want "display-manager.service" instead of > "graphical.target". > > You also will want "Requires=autofs.service". The distinction between > "After/Before" and "Requires" is exactly for the reason you give; the > ordering directives don't require anything, so

Re: [CentOS] systemd order help?

On Mon, Jun 12, 2017 at 03:47:46PM +, James Pearson wrote: > I'm guessing I could use something like: > > After=autofs.service > Before=graphical.target > > Is this correct? > > However, I would like to use the same systemd unit file on servers that > won't run X - will the above work?

Re: [CentOS] systemd order help?

Check out this page: https://scottlinux.com/2014/12/08/how-to-create-a-systemd-service-in-linux-centos-7/ On 12/06/17 11:47 AM, James Pearson wrote: I'm looking into 'porting' some custom init.d scripts that are in use on CentOS 6 boxes for use on CentOS 7 using systemd One particular init.d

[CentOS] systemd order help?

I'm looking into 'porting' some custom init.d scripts that are in use on CentOS 6 boxes for use on CentOS 7 using systemd One particular init.d script needs to run after autofs has been started, but before X11 is started I'm guessing I could use something like: After=autofs.service

Re: [CentOS] systemd missing something?

On 7 May 2017 at 16:30, Gordon Messmer wrote: > On 05/07/2017 07:22 AM, ken wrote: >> >> "Note that traditional init scripts continue to function on a systemd >> system. An init script /etc/rc.d/init.d/foobar is implicitly mapped >> into a service unit foobar.service

Re: [CentOS] systemd missing something?

On 05/07/2017 07:22 AM, ken wrote: "Note that traditional init scripts continue to function on a systemd system. An init script /etc/rc.d/init.d/foobar is implicitly mapped into a service unit foobar.service during system initialization." ... However, what it implies doesn't seem to work out.

Re: [CentOS] systemd missing something?

Am 07.05.2017 um 16:22 schrieb ken: "Note that traditional init scripts continue to function on a systemd system. An init script /etc/rc.d/init.d/foobar is implicitly mapped into a service unit foobar.service during system initialization." That's what it says in /etc/init.d/README. However,

[CentOS] systemd missing something?

"Note that traditional init scripts continue to function on a systemd system. An init script /etc/rc.d/init.d/foobar is implicitly mapped into a service unit foobar.service during system initialization." That's what it says in /etc/init.d/README. However, what it implies doesn't seem to work

  1   2   3   4   >