search for: oneshot

Hi all, I'm trying to resize a journal on my root filesystem. This is Ext3, kernel 2.4.19, latest e2fsprogs + htree patch. I've remounted my root filesystem as ext2, but still when I 'tune2fs -O ^has_journal' I get ---- The has_journal flag may only be cleared when the filesystem is unmounted or mounted read-only. ---- So, how can I increase the size of the journal? I

https://bugzilla.mindrot.org/show_bug.cgi?id=2231 Bug ID: 2231 Summary: Use EVP_Digest for oneshot digest calculation Product: Portable OpenSSH Version: 6.6p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: Miscellaneous Assignee: unassigned-bugs at mindrot.org...

I've been thinking a bit more about how useful an absolute timeout is for a oneshot timer in a virtual environment. In principle, absolute times are generally preferable. A relative timeout means "timeout in X ns from now", but the meaning of "now" is ambiguous, particularly if the vcpu can be preempted at any time, which means the determination of "now&...

I've been thinking a bit more about how useful an absolute timeout is for a oneshot timer in a virtual environment. In principle, absolute times are generally preferable. A relative timeout means "timeout in X ns from now", but the meaning of "now" is ambiguous, particularly if the vcpu can be preempted at any time, which means the determination of "now&...

...ad idea. It's not guaranteed that umount sync can finish > in time, Perhaps I misunderstand your comment, but I'm not worried about umount.target running late. That's not a problem. Finishing early would be a problem, but that's what the "Before" and the "Type=oneshot" is intended to handle. Quote from man systemd.service: Behavior of oneshot is similar to simple, however it is expected that the process has to exit before systemd starts follow-up units. By the way, "Before=umount.target" didn't seem to shock the systemd guys. > so y...

...t guaranteed that umount sync can >> finish in time, > > Perhaps I misunderstand your comment, but I'm not worried about > umount.target running late. That's not a problem. Finishing early would > be a problem, but that's what the "Before" and the "Type=oneshot" is > intended to handle. Type=oneshot does affect ordering Before=umount.target simply means you ask UPS to shutdown (with delay) before you start umounting disks and syncing changes > Quote from man systemd.service: Behavior of oneshot is similar to > simple, however it is ex...

...y, August 2, 2016 9:28 AM Subject: Re: [CentOS] centos 7- boot doesn't wait for startup script to complete On Tue, Aug 02, 2016 at 12:56:21PM +0000, KM wrote: > # used to set up the Myservices onstartup > [Unit] > Description=Start and stop Myservices > > [Service] > Type=oneshot > ExecStart=/etc/init.d/Myservices start > ExecStop=/etc/init.d/Myservices stop > RemainAfterExit=yes > > [Install] > WantedBy=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 b...

s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service base-addon-banner: starting ----------------------------------------------------------- Add-on: Network UPS Tools Manage battery backup (UPS) devices--------------------------------------------------...

...ration files. A new systemd service unit is needed to power off the UPS. The service unit consists of a new file /etc/systemd/system/ups-delayed-shutdown.service [Unit] Description=Initiate delayed UPS shutdown Before=umount.target DefaultDependencies=no [Service] Type=oneshot ExecStart=/usr/lib/ups/driver/upsdrvctl shutdown [Install] WantedBy=poweroff.target This service unit should be enabled with root command systemctl --system reenable /etc/systemd/system/ups-delayed-shutdown.service I have tested this setup with 64 bit openSUSE 12.3 and NUT 2.6.5...

...hutdown. ######## vPreShutdownHook.service ############### [Unit] Description=vPreShutdownHook Requires=network.target Requires=libvirtd.service Requires=dbus.service Requires=glusterd.service Requires=glusterfsd.service DefaultDependencies=no Before=shutdown.target reboot.target [Service] Type=oneshot RemainAfterExit=true ExecStart=/bin/true ExecStop=/root/vm_migrate.sh [Install] WantedBy=multi-user.target ########## Command to migrate ############ /usr/bin/virsh migrate --verbose --p2p --tunneled --live --compressed --comp-methods "mt" --comp-mt-level 5 --comp-mt-threads 5 --comp...

...; to power off the UPS. > > The service unit consists of a new file > /etc/systemd/system/ups-delayed-shutdown.service > > [Unit] > Description=Initiate delayed UPS shutdown > Before=umount.target > DefaultDependencies=no > > [Service] > Type=oneshot > ExecStart=/usr/lib/ups/driver/upsdrvctl shutdown > > [Install] > WantedBy=poweroff.target > > This service unit should be enabled with root command > > systemctl --system reenable > /etc/systemd/system/ups-delayed-shutdown.service > > I have tested...

...thought I'd throw it out there.? In either case, thanks for helping. > I looked online for an explanation of the options for these files, other that the systemd manual page which is hard to use.? I really couldn't find one.? Any suggestions? > Thanks again.KM Is your service still a oneshot type?? If you are starting daemonized services, systemd is probably terminating them. You should use a 'forking' type for services that will keep around processes. >? ? ? From: Jonathan Billings <billings at negate.org> > To: CentOS mailing list <centos at centos.org>...

...rto.pt <mailto:filipec at uporto.pt> >> > > Amazing this certbot thing... > > [Unit] > Description=Certbot > Documentation=file:///usr/share/doc/python-certbot-doc/html/index.html > Documentation=https://letsencrypt.readthedocs.io/en/latest/ > [Service] > Type=oneshot > ExecStart=/usr/bin/certbot -q renew --post-hook > /etc/letsencrypt/post.hooks.d/reload > PrivateTmp=true > > one would think this would work and reload nginx after the cert has > been renewed... > > Aki > -------------- next part -------------- An HTML attachment was sc...

hi,all I want the puppetd run in daemon only run by the puppetrun trigger, not schedule run . so how can do this ? what''s the maximum of the runinterval ? I want change this option to do this. Please help me . -- Huang Mingyou

Good Evening, I recently purchased an EPYC quantum UPS. I installed NUT on the home assistant by connecting the UPS via USB and tried all the various drivers in the list, the only one that seems to work is: usbhid-ups with this log: s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service base-addon-banner: starting ----------------------------------------------------------- Add-on: Network UPS Tools Manage battery backup (UPS) devices ----------------------------------------------...

...thought I'd throw it out there.? In either case, thanks for helping. > I looked online for an explanation of the options for these files, other that the systemd manual page which is hard to use.? I really couldn't find one.? Any suggestions? > Thanks again.KM Is your service still a oneshot type?? If you are starting daemonized services, systemd is probably terminating them. You should use a 'forking' type for services that will keep around processes. >? ? ? From: Jonathan Billings <billings at negate.org> > To: CentOS mailing list <centos at centos.org>...

...ctl start dovecot' it breaks with a dependency error which comes from dovecot-init.service. dovecot-init.service : [Unit] Description=One-time Dovecot init service ConditionPathExists=|!/var/lib/dovecot/ssl-parameters.dat ConditionPathExists=|!/etc/pki/dovecot/certs/dovecot.pem [Service] Type=oneshot RemainAfterExit=no ExecStart=/bin/sh -c '\ if [ ! -f /etc/pki/dovecot/certs/dovecot.pem ]; \ then\ ? SSLDIR=/etc/pki/dovecot/ OPENSSLCONFIG=/etc/pki/dovecot/dovecot-openssl.cnf /usr/libexec/dovecot/mkcert.sh /dev/null 2>&1;\ fi;\ if [ ! -f /var/lib/dovecot/ssl-parameters.dat ]; \ then\ ?...

...thought I'd throw it out there. In either case, thanks for helping. > I looked online for an explanation of the options for these files, other that the systemd manual page which is hard to use. I really couldn't find one. Any suggestions? > Thanks again.KM Is your service still a oneshot type? If you are starting daemonized services, systemd is probably terminating them. You should use a 'forking' type for services that will keep around processes. > From: Jonathan Billings <billings at negate.org> > To: CentOS mailing list <centos at centos.org>...

Hi, It would be preferable to use EVP_Digest for oneshot digest calculation: - one calloc/free less - EVP_Digest properly sets oneshot flag (certain hardware accelerators work only if the flag is set) Please consider applying the following patch: diff -ru openssh-6.6p1.orig/digest-openssl.c openssh-6.6p1/digest-openssl.c --- openssh-6.6p1.orig/dig...

...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 stopRemainAfterExit=yes[Install]WantedBy=multi-user.targetThis works. When the server starts Myservices is initiated.? However the boot keeps going. When I log in Myservices is still running.? it takes about 5 minutes to complete....