search for: timeoutstartsec

...tedBy=multi-user.target Reformatting so it is readable. What you probably want to do is to add something to the [Unit] section to make the completion of the be a requirement for the user login service.? Something like: Before=systemd-user-sessions.service You will most likely also need to add a TimeoutStartSec= to your [Service] section to give it a longer time to run before systemd times out the service start. -- Jonathan Billings <billings at negate.org> _______________________________________________ CentOS mailing list CentOS at centos.org https://lists.centos.org/mailman/listinfo/centos

...gt;to be online. In the [Unit] section add Wants=network-online.target. > >Secondly, I'd try to find a way for the auxiliary services to ping the >prime service to ensure its up, and make that script a ExecStartPre >entry in the [Service] section. You'll want to adjust the >TimeoutStartSec in case it might exceed the DefaultTimeoutStartSec in >/etc/systemd/system.conf, which is 90 seconds. Thank you for the idea, but as mentioned, the same service runs on a mix of server platforms and distros, and the older ones do not use systemd, so I'd prefer to stick with SysV type initsc...

Hi All,I have a general question.? I have an old rc type startup script that I am still using on CentOS 7.? I got it to run by creating the systemd service file... a simple one as shown below, for Myservices. # used to set up the Myservices onstartup[Unit]Description=Start and stop Myservices[Service]Type=oneshotExecStart=/etc/init.d/Myservices startExecStop=/etc/init.d/Myservices

James Hogarth <james.hogarth at gmail.com> wrote: >On 18 Dec 2016 10:59, "whitivery" <co55-sy1t at dea.spamcon.org> wrote: > >Moving from CentOS 5 to CentOS 7, discovered that a test in a SysV >initscript for whether it is running interactively, instead of at boot >time, no longer works. > >Under CentOS 7 / systemd, is there some way for the initscript

...> If your on Raspbian. > Run : sudo raspi-config > Check what the state is of : Wait for Network at Boot. It is set to "No" > > Is someone using something like this to reduce boot time? > /etc/systemd/system/networking.service.d/reduce-timeout.conf > [Service] > TimeoutStartSec=1 I'm not. > Roy, can you reboot the pi and send me the dmesg log and syslog I found some reports about "faulty" Pi mainboards also. > Or can you check it and look flipping networks.. > > Something like this: > [ 182.553342] bcmgenet fd580000.genet eth0: Link is Down...

...it is readable. > > What you probably want to do is to add something to the [Unit] section > to make the completion of the be a requirement for the user login > service.? Something like: > > Before=systemd-user-sessions.service > > You will most likely also need to add a TimeoutStartSec= to your > [Service] section to give it a longer time to run before systemd times > out the service start. > > > -- > Jonathan Billings <billings at negate.org> > _______________________________________________ > CentOS mailing list > CentOS at centos.org > ht...

The particular issue is with puppetmaster (which admittedly takes 4 minutes to actually start, setting TimeoutStartSec=300 in it's unit file stopped the false timeout report) but I have seen it one other time (don't remember the details). systemctl status puppetmaster ? puppetmaster.service - Puppet master Loaded: loaded (/lib/systemd/system/puppetmaster.service; enabled; vendor preset: enabled) Active...

...it is readable. > > What you probably want to do is to add something to the [Unit] section > to make the completion of the be a requirement for the user login > service.? Something like: > > Before=systemd-user-sessions.service > > You will most likely also need to add a TimeoutStartSec= to your > [Service] section to give it a longer time to run before systemd times > out the service start. > > > -- > Jonathan Billings <billings at negate.org> > _______________________________________________ > CentOS mailing list > CentOS at centos.org > ht...

On Mon, Jul 18, 2016 at 08:06:59PM +0300, Eero Volotinen wrote: > > Try this > https://ask.fedoraproject.org/en/question/26898/what-is-the-auto-start-file-like-rclocal/ Note: the accepted answer there is wrong, it should be /etc/rc.d/rc.local, not /etc/rc.local. Anyway, using /etc/rc.d/rc.local won't be much different from what the current service is doing. -- Jonathan Billings

...tedBy=multi-user.target Reformatting so it is readable. What you probably want to do is to add something to the [Unit] section to make the completion of the be a requirement for the user login service. Something like: Before=systemd-user-sessions.service You will most likely also need to add a TimeoutStartSec= to your [Service] section to give it a longer time to run before systemd times out the service start. -- Jonathan Billings <billings at negate.org>

...it is readable. > > What you probably want to do is to add something to the [Unit] section > to make the completion of the be a requirement for the user login > service. Something like: > > Before=systemd-user-sessions.service > > You will most likely also need to add a TimeoutStartSec= to your > [Service] section to give it a longer time to run before systemd times > out the service start. > > > -- > Jonathan Billings <billings at negate.org> > _______________________________________________ > CentOS mailing list > CentOS at centos.org > ht...

...e wait for the network to be online. In the [Unit] section add Wants=network-online.target. Secondly, I'd try to find a way for the auxiliary services to ping the prime service to ensure its up, and make that script a ExecStartPre entry in the [Service] section. You'll want to adjust the TimeoutStartSec in case it might exceed the DefaultTimeoutStartSec in /etc/systemd/system.conf, which is 90 seconds. -- Jonathan Billings <billings at negate.org>

On 29 Aug 2017 17:58, "Leroy Tennison" <leroy at datavoiceint.com> wrote: The particular issue is with puppetmaster (which admittedly takes 4 minutes to actually start, setting TimeoutStartSec=300 in it's unit file stopped the false timeout report) but I have seen it one other time (don't remember the details). systemctl status puppetmaster ? puppetmaster.service - Puppet master Loaded: loaded (/lib/systemd/system/puppetmaster.service; enabled; vendor preset: enabled) Active: fa...

...ent: Tuesday, August 29, 2017 2:03:44 PM Subject: Re: [CentOS] Syncronize systemctl status with reality? On 29 Aug 2017 17:58, "Leroy Tennison" <leroy at datavoiceint.com> wrote: The particular issue is with puppetmaster (which admittedly takes 4 minutes to actually start, setting TimeoutStartSec=300 in it's unit file stopped the false timeout report) but I have seen it one other time (don't remember the details). systemctl status puppetmaster ? puppetmaster.service - Puppet master Loaded: loaded (/lib/systemd/system/puppetmaster.service; enabled; vendor preset: enabled) Active: fa...

...do raspi-config > > Check what the state is of : Wait for Network at Boot. > It is set to "No" > > > > > Is someone using something like this to reduce boot time? > > /etc/systemd/system/networking.service.d/reduce-timeout.conf > > [Service] > > TimeoutStartSec=1 > I'm not. > > > Roy, can you reboot the pi and send me the dmesg log and > syslog I found some reports about "faulty" Pi mainboards also. > > Or can you check it and look flipping networks.. > > > > Something like this: > > [ 182.553342] b...

Roy, Im still wondering what your problem might be/where its coming from. But we know it's interface/network related, only thing is Samba should not coredump. So i had a good look below to see where im missing what. And i dont see much to work with. I have 2 possible options where, where a problem might be. 1) samba start before network is online. A possible workaround is add in all

...uys can confirm the os once again, who runs which one exactly. If your on Raspbian. Run : sudo raspi-config Check what the state is of : Wait for Network at Boot. Is someone using something like this to reduce boot time? /etc/systemd/system/networking.service.d/reduce-timeout.conf [Service] TimeoutStartSec=1 Roy, can you reboot the pi and send me the dmesg log and syslog I found some reports about "faulty" Pi mainboards also. Or can you check it and look flipping networks.. Something like this: [ 182.553342] bcmgenet fd580000.genet eth0: Link is Down [ 182.553465] br0: port 1(eth0) en...