[opensuse] systemd - spamd.service: Start operation timed out. Terminating.
I'm trying to start spamd on Leap 15.1 - somehow systemd does not recognise it has been started and then kills it. # systemctl cat spamd [snip] [Service] Type=forking PIDFile=/var/run/spamd.pid ExecStartPre=/bin/bash -c "sa-update || true" EnvironmentFile=-/etc/sysconfig/spamd ExecStart=/usr/sbin/spamd $SPAMD_ARGS -r /var/run/spamd.pid ExecReload=/usr/bin/kill -HUP $MAINPID Seems to me the pidfile is fine ? -- Per Jessen, Zürich (29.0°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
I'm trying to start spamd on Leap 15.1 - somehow systemd does not recognise it has been started and then kills it.
# systemctl cat spamd [snip] [Service] Type=forking PIDFile=/var/run/spamd.pid ExecStartPre=/bin/bash -c "sa-update || true" EnvironmentFile=-/etc/sysconfig/spamd ExecStart=/usr/sbin/spamd $SPAMD_ARGS -r /var/run/spamd.pid ExecReload=/usr/bin/kill -HUP $MAINPID
Seems to me the pidfile is fine ?
The same or a very similar problem is reported here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775578 -- Per Jessen, Zürich (29.2°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 19 Jun 2019 18:29, Per Jessen wrote:
Per Jessen wrote:
I'm trying to start spamd on Leap 15.1 - somehow systemd does not recognise it has been started and then kills it.
# systemctl cat spamd [snip] [Service] Type=forking PIDFile=/var/run/spamd.pid ExecStartPre=/bin/bash -c "sa-update || true" EnvironmentFile=-/etc/sysconfig/spamd ExecStart=/usr/sbin/spamd $SPAMD_ARGS -r /var/run/spamd.pid ExecReload=/usr/bin/kill -HUP $MAINPID
Seems to me the pidfile is fine ?
The same or a very similar problem is reported here:
Just a hint: Under certain conditions spamd takes longer to start. If that time reaches the "DefaultTimeoutStartSec"[1] of systemd the behavior gets "erratic" to say at least. Best way to solve the problem in the long run would be the inclusion of a line with "TimeoutStartSec=120s" [2] into the spamd.service file. That is at least my opinion. Docu / Info: [1] man systemd-system.conf [2] man systemd.service - Yamaban. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Yamaban wrote:
On Wed, 19 Jun 2019 18:29, Per Jessen wrote:
Per Jessen wrote:
I'm trying to start spamd on Leap 15.1 - somehow systemd does not recognise it has been started and then kills it.
# systemctl cat spamd [snip] [Service] Type=forking PIDFile=/var/run/spamd.pid ExecStartPre=/bin/bash -c "sa-update || true" EnvironmentFile=-/etc/sysconfig/spamd ExecStart=/usr/sbin/spamd $SPAMD_ARGS -r /var/run/spamd.pid ExecReload=/usr/bin/kill -HUP $MAINPID
Seems to me the pidfile is fine ?
The same or a very similar problem is reported here:
Just a hint: Under certain conditions spamd takes longer to start.
Yep, I'm well aware.
Best way to solve the problem in the long run would be the inclusion of a line with "TimeoutStartSec=120s" [2] into the spamd.service file. That is at least my opinion.
Thanks for chipping in - an extra pair of eyes is always useful. In this case it was easy .... The service unit has type=forking, for whatever reason. In my setup, spamd does not fork so I need type=simple. I have amended /etc/sysconfig/spamd::SPAMD_ARGS, so I no longer know what the original SPAMD_ARGS were. -- Per Jessen, Zürich (28.2°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 19/06/2019 19.34, Per Jessen wrote:
Yamaban wrote:
On Wed, 19 Jun 2019 18:29, Per Jessen wrote: ...
The service unit has type=forking, for whatever reason. In my setup, spamd does not fork so I need type=simple. I have amended /etc/sysconfig/spamd::SPAMD_ARGS, so I no longer know what the original SPAMD_ARGS were.
# The arguments passed to spamd. # See spamd(1) man page. # Default is "-d -c -L" SPAMD_ARGS="-d -c -L" -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Carlos E. R. wrote:
On 19/06/2019 19.34, Per Jessen wrote:
Yamaban wrote:
On Wed, 19 Jun 2019 18:29, Per Jessen wrote: ...
The service unit has type=forking, for whatever reason. In my setup, spamd does not fork so I need type=simple. I have amended /etc/sysconfig/spamd::SPAMD_ARGS, so I no longer know what the original SPAMD_ARGS were.
# The arguments passed to spamd. # See spamd(1) man page. # Default is "-d -c -L" SPAMD_ARGS="-d -c -L"
Thanks - so iow, mea culpa. -- Per Jessen, Zürich (28.1°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 19/06/2019 19.40, Per Jessen wrote:
Carlos E. R. wrote:
On 19/06/2019 19.34, Per Jessen wrote:
Yamaban wrote:
On Wed, 19 Jun 2019 18:29, Per Jessen wrote: ...
The service unit has type=forking, for whatever reason. In my setup, spamd does not fork so I need type=simple. I have amended /etc/sysconfig/spamd::SPAMD_ARGS, so I no longer know what the original SPAMD_ARGS were.
# The arguments passed to spamd. # See spamd(1) man page. # Default is "-d -c -L" SPAMD_ARGS="-d -c -L"
Thanks - so iow, mea culpa.
Oh, just in case you deleted the comment :-) My main machine says different: # Default is "-d -c -a -L" SPAMD_ARGS="-d -c --max-children=16 --max-conn-per-child=1" Can be from a decade ago. The one I posted first was from a laptop I installed this summer. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 19/06/2019 18.00, Per Jessen wrote:
I'm trying to start spamd on Leap 15.1 - somehow systemd does not recognise it has been started and then kills it.
# systemctl cat spamd [snip] [Service] Type=forking PIDFile=/var/run/spamd.pid ExecStartPre=/bin/bash -c "sa-update || true" EnvironmentFile=-/etc/sysconfig/spamd ExecStart=/usr/sbin/spamd $SPAMD_ARGS -r /var/run/spamd.pid ExecReload=/usr/bin/kill -HUP $MAINPID
Yes, you have to increase the timeout. /etc/systemd/system.conf DefaultTimeoutStartSec=100s #DefaultTimeoutStopSec=90s I don't know if it is possible to change the timeout for an specific service only. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Am Mittwoch, 19. Juni 2019, 19:24:22 CEST schrieb Carlos E. R.:
On 19/06/2019 18.00, Per Jessen wrote:
I'm trying to start spamd on Leap 15.1 - somehow systemd does not recognise it has been started and then kills it.
# systemctl cat spamd [snip] [Service] Type=forking PIDFile=/var/run/spamd.pid ExecStartPre=/bin/bash -c "sa-update || true" EnvironmentFile=-/etc/sysconfig/spamd ExecStart=/usr/sbin/spamd $SPAMD_ARGS -r /var/run/spamd.pid ExecReload=/usr/bin/kill -HUP $MAINPID
Yes, you have to increase the timeout.
/etc/systemd/system.conf
DefaultTimeoutStartSec=100s #DefaultTimeoutStopSec=90s
I don't know if it is possible to change the timeout for an specific service only.
systemctl edit spamd.service and then you put in that file that opens in your editor: [Service] TimeoutSec=5min cheers MH -- Mathias Homann Senior Systems Engineer, IT Consultant. IT Trainer Mathias.Homann@openSUSE.org http://www.tuxonline.tech gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102
On 20/06/2019 07.25, Mathias Homann wrote:
Am Mittwoch, 19. Juni 2019, 19:24:22 CEST schrieb Carlos E. R.:
On 19/06/2019 18.00, Per Jessen wrote:
I'm trying to start spamd on Leap 15.1 - somehow systemd does not recognise it has been started and then kills it.
# systemctl cat spamd [snip] [Service] Type=forking PIDFile=/var/run/spamd.pid ExecStartPre=/bin/bash -c "sa-update || true" EnvironmentFile=-/etc/sysconfig/spamd ExecStart=/usr/sbin/spamd $SPAMD_ARGS -r /var/run/spamd.pid ExecReload=/usr/bin/kill -HUP $MAINPID
Yes, you have to increase the timeout.
/etc/systemd/system.conf
DefaultTimeoutStartSec=100s #DefaultTimeoutStopSec=90s
I don't know if it is possible to change the timeout for an specific service only.
systemctl edit spamd.service
OHHH! :-o Cute! :-)
and then you put in that file that opens in your editor:
[Service] TimeoutSec=5min
File /etc/systemd/system/spamd.service.d/.#override.conf4232f2d9628a1852 saved If '[Service]' is not a typo you can use command-not-found to lookup the package that contains it, like this: cnf [Service] (see below, end of post) Two files appear: Legolas:~ # l /etc/systemd/system/spamd.service.d/ total 12 drwxr-xr-x 2 root root 4096 Jun 20 11:45 ./ -rw-r--r-- 1 root root 0 Jun 20 11:44 .#override.conf4232f2d9628a1852~ drwxr-xr-x 16 root root 4096 Jun 20 11:44 ../ -rw-r--r-- 1 root root 26 Jun 20 11:45 override.conf The first one seems to be an empty backup, created by jstar on save file. If I edit several times, I get several random backups: Legolas:~ # l /etc/systemd/system/spamd.service.d/ total 20 drwxr-xr-x 2 root root 4096 Jun 20 11:53 ./ -rw-r--r-- 1 root root 26 Jun 20 11:50 .#override.conf748b335726843cc8~ -rw-r--r-- 1 root root 26 Jun 20 11:45 .#override.confb7ef8420ac9e17ac~ drwxr-xr-x 16 root root 4096 Jun 20 11:44 ../ -rw-r--r-- 1 root root 27 Jun 20 11:53 override.conf Legolas:~ # [...] Oh, now I know what the first error was above: the editor took several seconds to start, so I thought I was already at some unknown editor and started to type, while it was still the bash command line. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Am Donnerstag, 20. Juni 2019, 11:56:43 CEST schrieb Carlos E.R.:
systemctl edit spamd.service
OHHH! :-o
Cute! :-)
and then you put in that file that opens in your editor:
[Service] TimeoutSec=5min
In theory such an override file can contain any configuration option that would appear in a .service file, so you could even make your apache start nginx instead of apache, if you feel that frisky... Cheers MH -- Mathias Homann Senior Systems Engineer, IT Consultant. IT Trainer Mathias.Homann@openSUSE.org http://www.tuxonline.tech gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, 20 Jun 2019 11:56:43 +0200 "Carlos E.R." <robin.listas@gmx.es> wrote:
On 20/06/2019 07.25, Mathias Homann wrote:
Am Mittwoch, 19. Juni 2019, 19:24:22 CEST schrieb Carlos E. R.:
On 19/06/2019 18.00, Per Jessen wrote:
I'm trying to start spamd on Leap 15.1 - somehow systemd does not recognise it has been started and then kills it.
# systemctl cat spamd [snip] [Service] Type=forking PIDFile=/var/run/spamd.pid ExecStartPre=/bin/bash -c "sa-update || true" EnvironmentFile=-/etc/sysconfig/spamd ExecStart=/usr/sbin/spamd $SPAMD_ARGS -r /var/run/spamd.pid ExecReload=/usr/bin/kill -HUP $MAINPID
Yes, you have to increase the timeout.
/etc/systemd/system.conf
DefaultTimeoutStartSec=100s #DefaultTimeoutStopSec=90s
I don't know if it is possible to change the timeout for an specific service only.
systemctl edit spamd.service
OHHH! :-o
Cute! :-)
and then you put in that file that opens in your editor:
[Service] TimeoutSec=5min
File /etc/systemd/system/spamd.service.d/.#override.conf4232f2d9628a1852 saved If '[Service]' is not a typo you can use command-not-found to lookup the package that contains it, like this: cnf [Service]
(see below, end of post)
Two files appear:
Legolas:~ # l /etc/systemd/system/spamd.service.d/ total 12 drwxr-xr-x 2 root root 4096 Jun 20 11:45 ./ -rw-r--r-- 1 root root 0 Jun 20 11:44 .#override.conf4232f2d9628a1852~ drwxr-xr-x 16 root root 4096 Jun 20 11:44 ../ -rw-r--r-- 1 root root 26 Jun 20 11:45 override.conf
The first one seems to be an empty backup, created by jstar on save file. If I edit several times, I get several random backups:
Sounds most likely to be a bug in your editor - jstar? I would try say nano and see if the problem persists. If so, it must be a bug in the way systemd edit is calling/using the editor but then I'd expect a lot more people to be encountering it. Anyway, a bit more investigation needed to track it down. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Dave Howorth wrote:
Sounds most likely to be a bug in your editor - jstar? I would try say nano
I get nano by default, but no doubt there is a config option somewhere. -- Per Jessen, Zürich (18.6°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Per Jessen <per@computer.org> [06-20-19 06:57]:
Dave Howorth wrote:
Sounds most likely to be a bug in your editor - jstar? I would try say nano
I get nano by default, but no doubt there is a config option somewhere.
maybe enlightening: man systemctl in edit UNIT... Edit a drop-in snippet or a whole replacement file if --full is specified, to extend or override the specified unit. Depending on whether --system (the default), --user, or --global is specified, this command creates a drop-in file for each unit either for the system, for the calling user, or for all futures logins of all users. Then, the editor (see the "Environment" section below) is invoked on temporary files which will be written to the real location if the editor exits successfully. If --full is specified, this will copy the original units instead of creating drop-in files. If --force is specified and any units do not already exist, new unit files will be opened for editing. If --runtime is specified, the changes will be made temporarily in /run and they will be lost on the next reboot. If the temporary file is empty upon exit, the modification of the related unit is canceled. After the units have been edited, systemd configuration is reloaded (in a way that is equivalent to daemon-reload). daemon-reload). -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 20/06/2019 12.56, Per Jessen wrote:
Dave Howorth wrote:
Sounds most likely to be a bug in your editor - jstar? I would try say nano
I get nano by default, but no doubt there is a config option somewhere.
The editor is jstar because I have the enviroment variable: Legolas:~ # set | grep -i editor EDITOR=/usr/bin/jstar No, there is no bug in jstar. jstar creates a backup file automatically. The name is provided by systemd. The command "crontab -e" edits the crontab file, and there is no issue with random backups, so the bug is in systemd: Legolas:~ # crontab -e ... File /tmp/crontab.p1XWIq saved crontab: installing new crontab Legolas:~ # l /tmp/crontab.p1XWIq ls: cannot access '/tmp/crontab.p1XWIq': No such file or directory Legolas:~ # l /tmp/crontab* -rw------- 1 root root 0 Jan 1 1970 /tmp/crontab.p1XWIq~ Legolas:~ # But it is in /tmp, where it can be easily purged periodically. Legolas:~ # l /var/spool/cron/tabs/ total 12 drwx------ 2 root root 4096 Jun 20 13:45 ./ drwx------ 4 root root 4096 Jun 17 2018 ../ -rw------- 1 root root 144 Jun 20 13:45 root Legolas:~ # -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On Thu, 20 Jun 2019 13:51:55 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 20/06/2019 12.56, Per Jessen wrote:
Dave Howorth wrote:
Sounds most likely to be a bug in your editor - jstar? I would try say nano
I get nano by default, but no doubt there is a config option somewhere.
The editor is jstar because I have the enviroment variable:
Legolas:~ # set | grep -i editor EDITOR=/usr/bin/jstar
No, there is no bug in jstar. jstar creates a backup file automatically. The name is provided by systemd.
The command "crontab -e" edits the crontab file, and there is no issue with random backups, so the bug is in systemd:
Legolas:~ # crontab -e
...
File /tmp/crontab.p1XWIq saved crontab: installing new crontab Legolas:~ # l /tmp/crontab.p1XWIq ls: cannot access '/tmp/crontab.p1XWIq': No such file or directory Legolas:~ # l /tmp/crontab* -rw------- 1 root root 0 Jan 1 1970 /tmp/crontab.p1XWIq~ Legolas:~ #
But it is in /tmp, where it can be easily purged periodically.
Legolas:~ # l /var/spool/cron/tabs/ total 12 drwx------ 2 root root 4096 Jun 20 13:45 ./ drwx------ 4 root root 4096 Jun 17 2018 ../ -rw------- 1 root root 144 Jun 20 13:45 root Legolas:~ #
Well I don't get a file left behind by editing crontab (which uses vim on my system) or by editing a systemd service file (which uses nano on my system). So either: it's a newly introduced bug (I'm on 15.0) or it is editor-related or both I still suggest you try the edit using the default (nano) and then report the bug. If you report it with a non-standard editor that's the first question to be asked. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
It's editor related - happens to me too, my $EDITOR and $VISUAL point at /usr/bin/joe Cheers MH On 20.06.2019 16:40, Dave Howorth wrote:
On Thu, 20 Jun 2019 13:51:55 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 20/06/2019 12.56, Per Jessen wrote:
Dave Howorth wrote:
Sounds most likely to be a bug in your editor - jstar? I would try say nano I get nano by default, but no doubt there is a config option somewhere. The editor is jstar because I have the enviroment variable:
Legolas:~ # set | grep -i editor EDITOR=/usr/bin/jstar
No, there is no bug in jstar. jstar creates a backup file automatically. The name is provided by systemd.
The command "crontab -e" edits the crontab file, and there is no issue with random backups, so the bug is in systemd:
Legolas:~ # crontab -e
...
File /tmp/crontab.p1XWIq saved crontab: installing new crontab Legolas:~ # l /tmp/crontab.p1XWIq ls: cannot access '/tmp/crontab.p1XWIq': No such file or directory Legolas:~ # l /tmp/crontab* -rw------- 1 root root 0 Jan 1 1970 /tmp/crontab.p1XWIq~ Legolas:~ #
But it is in /tmp, where it can be easily purged periodically.
Legolas:~ # l /var/spool/cron/tabs/ total 12 drwx------ 2 root root 4096 Jun 20 13:45 ./ drwx------ 4 root root 4096 Jun 17 2018 ../ -rw------- 1 root root 144 Jun 20 13:45 root Legolas:~ # Well I don't get a file left behind by editing crontab (which uses vim on my system) or by editing a systemd service file (which uses nano on my system). So either:
it's a newly introduced bug (I'm on 15.0) or it is editor-related or both
I still suggest you try the edit using the default (nano) and then report the bug. If you report it with a non-standard editor that's the first question to be asked.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, 20 Jun 2019 17:55:53 +0200 Mathias Homann <Mathias.Homann@opensuse.org> wrote:
It's editor related - happens to me too, my $EDITOR and $VISUAL point at /usr/bin/joe
Yup. $ sudo EDITOR=/usr/bin/jstar systemctl edit --system apache2 $ ls -la /etc/systemd/system/apache2.service.d/ total 8 drwxr-xr-x 1 root root 90 Jun 20 17:12 ./ drwxr-xr-x 1 root root 1622 Jun 20 15:31 ../ -rw-r--r-- 1 root root 27 Jun 20 17:12 override.conf -rw-r--r-- 1 root root 10 Jun 20 15:31 .#override.conf3934306d53707dd5~ So not new but definitely editor-related -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 20/06/2019 18.14, Dave Howorth wrote:
On Thu, 20 Jun 2019 17:55:53 +0200 Mathias Homann <Mathias.Homann@opensuse.org> wrote:
It's editor related - happens to me too, my $EDITOR and $VISUAL point at /usr/bin/joe
Yup.
$ sudo EDITOR=/usr/bin/jstar systemctl edit --system apache2 $ ls -la /etc/systemd/system/apache2.service.d/ total 8 drwxr-xr-x 1 root root 90 Jun 20 17:12 ./ drwxr-xr-x 1 root root 1622 Jun 20 15:31 ../ -rw-r--r-- 1 root root 27 Jun 20 17:12 override.conf -rw-r--r-- 1 root root 10 Jun 20 15:31 .#override.conf3934306d53707dd5~
So not new but definitely editor-related
Try another editor that creates backups. The problem will be there. There are three solutions: create the temporary file on a temporary directory, such as /tmp, edit then move to final destination. This is what what crontab does. Make the call to the EDITOR in some manner that disables backups - but this will affect any other use of EDITOR by other calls. Disable edit file backup altogether in joe - again, this affects other jobs. The first one I think is better, and that lands it at systemd table. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On Thu, 20 Jun 2019 18:50:03 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 20/06/2019 18.14, Dave Howorth wrote:
On Thu, 20 Jun 2019 17:55:53 +0200 Mathias Homann <Mathias.Homann@opensuse.org> wrote:
It's editor related - happens to me too, my $EDITOR and $VISUAL point at /usr/bin/joe
Yup.
$ sudo EDITOR=/usr/bin/jstar systemctl edit --system apache2 $ ls -la /etc/systemd/system/apache2.service.d/ total 8 drwxr-xr-x 1 root root 90 Jun 20 17:12 ./ drwxr-xr-x 1 root root 1622 Jun 20 15:31 ../ -rw-r--r-- 1 root root 27 Jun 20 17:12 override.conf -rw-r--r-- 1 root root 10 Jun 20 15:31 .#override.conf3934306d53707dd5~
So not new but definitely editor-related
Try another editor that creates backups. The problem will be there.
I already told you it wasn't; here's the proof: $ sudo EDITOR=/usr/bin/vim systemctl edit --system apache2 $ ls -la /etc/systemd/system/apache2.service.d/ total 4 drwxr-xr-x 1 root root 26 Jun 20 20:02 ./ drwxr-xr-x 1 root root 1622 Jun 20 20:02 ../ -rw-r--r-- 1 root root 10 Jun 20 20:02 override.conf and yes it was editing ...service.d/.#override.confb43e88ab28a12419 -rw-r--r-- 1 root root 10 Jun 20 20:02 .#override.confb43e88ab28a12419 -rw-r--r-- 1 root root 12288 Jun 20 20:03 .#override.confb43e88ab28a12419.swp
There are three solutions:
You missed out the obvious solution: create the temporary file in place in the final directory (which serves to check that the directory is now present with adequate permissions) then rename it to the final name upon exit.
create the temporary file on a temporary directory, such as /tmp, edit then move to final destination. This is what what crontab does.
but there's no temporary file left in tmp when vim edits a crontab, just as there's no temporary file in the override directory when vim edits a service file
Make the call to the EDITOR in some manner that disables backups - but this will affect any other use of EDITOR by other calls.
Disable edit file backup altogether in joe - again, this affects other jobs.
The first one I think is better, and that lands it at systemd table.
The left over file is only present when you use jstar, not any other editor. So how is this systemd's fault? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Dave Howorth wrote:
but there's no temporary file left in tmp when vim edits a crontab, just as there's no temporary file in the override directory when vim edits a service file
Fwiw, I concur. Same behaviour with vim. -- Per Jessen, Zürich (18.0°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 20/06/2019 21.14, Dave Howorth wrote:
On Thu, 20 Jun 2019 18:50:03 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 20/06/2019 18.14, Dave Howorth wrote:
On Thu, 20 Jun 2019 17:55:53 +0200 Mathias Homann <Mathias.Homann@opensuse.org> wrote:
It's editor related - happens to me too, my $EDITOR and $VISUAL point at /usr/bin/joe
Yup.
$ sudo EDITOR=/usr/bin/jstar systemctl edit --system apache2 $ ls -la /etc/systemd/system/apache2.service.d/ total 8 drwxr-xr-x 1 root root 90 Jun 20 17:12 ./ drwxr-xr-x 1 root root 1622 Jun 20 15:31 ../ -rw-r--r-- 1 root root 27 Jun 20 17:12 override.conf -rw-r--r-- 1 root root 10 Jun 20 15:31 .#override.conf3934306d53707dd5~
So not new but definitely editor-related
Try another editor that creates backups. The problem will be there.
I already told you it wasn't; here's the proof:
$ sudo EDITOR=/usr/bin/vim systemctl edit --system apache2 $ ls -la /etc/systemd/system/apache2.service.d/ total 4 drwxr-xr-x 1 root root 26 Jun 20 20:02 ./ drwxr-xr-x 1 root root 1622 Jun 20 20:02 ../ -rw-r--r-- 1 root root 10 Jun 20 20:02 override.conf
and yes it was editing ...service.d/.#override.confb43e88ab28a12419
-rw-r--r-- 1 root root 10 Jun 20 20:02 .#override.confb43e88ab28a12419 -rw-r--r-- 1 root root 12288 Jun 20 20:03 .#override.confb43e88ab28a12419.swp
There are three solutions:
You missed out the obvious solution:
create the temporary file in place in the final directory (which serves to check that the directory is now present with adequate permissions) then rename it to the final name upon exit.
create the temporary file on a temporary directory, such as /tmp, edit then move to final destination. This is what what crontab does.
but there's no temporary file left in tmp when vim edits a crontab, just as there's no temporary file in the override directory when vim edits a service file
Make the call to the EDITOR in some manner that disables backups - but this will affect any other use of EDITOR by other calls.
Disable edit file backup altogether in joe - again, this affects other jobs.
The first one I think is better, and that lands it at systemd table.
The left over file is only present when you use jstar, not any other editor. So how is this systemd's fault?
I repeat: try any other editor that creates backup files by default. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On Thu, 20 Jun 2019 22:26:02 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 20/06/2019 21.14, Dave Howorth wrote:
On Thu, 20 Jun 2019 18:50:03 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 20/06/2019 18.14, Dave Howorth wrote:
On Thu, 20 Jun 2019 17:55:53 +0200 Mathias Homann <Mathias.Homann@opensuse.org> wrote:
It's editor related - happens to me too, my $EDITOR and $VISUAL point at /usr/bin/joe
Yup.
$ sudo EDITOR=/usr/bin/jstar systemctl edit --system apache2 $ ls -la /etc/systemd/system/apache2.service.d/ total 8 drwxr-xr-x 1 root root 90 Jun 20 17:12 ./ drwxr-xr-x 1 root root 1622 Jun 20 15:31 ../ -rw-r--r-- 1 root root 27 Jun 20 17:12 override.conf -rw-r--r-- 1 root root 10 Jun 20 15:31 .#override.conf3934306d53707dd5~
So not new but definitely editor-related
Try another editor that creates backups. The problem will be there.
I already told you it wasn't; here's the proof:
$ sudo EDITOR=/usr/bin/vim systemctl edit --system apache2 $ ls -la /etc/systemd/system/apache2.service.d/ total 4 drwxr-xr-x 1 root root 26 Jun 20 20:02 ./ drwxr-xr-x 1 root root 1622 Jun 20 20:02 ../ -rw-r--r-- 1 root root 10 Jun 20 20:02 override.conf
and yes it was editing ...service.d/.#override.confb43e88ab28a12419
-rw-r--r-- 1 root root 10 Jun 20 20:02 .#override.confb43e88ab28a12419 -rw-r--r-- 1 root root 12288 Jun 20 20:03 .#override.confb43e88ab28a12419.swp
There are three solutions:
You missed out the obvious solution:
create the temporary file in place in the final directory (which serves to check that the directory is now present with adequate permissions) then rename it to the final name upon exit.
create the temporary file on a temporary directory, such as /tmp, edit then move to final destination. This is what what crontab does.
but there's no temporary file left in tmp when vim edits a crontab, just as there's no temporary file in the override directory when vim edits a service file
Make the call to the EDITOR in some manner that disables backups - but this will affect any other use of EDITOR by other calls.
Disable edit file backup altogether in joe - again, this affects other jobs.
The first one I think is better, and that lands it at systemd table.
The left over file is only present when you use jstar, not any other editor. So how is this systemd's fault?
I repeat: try any other editor that creates backup files by default.
You mean like vim does? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 20/06/2019 22.29, Dave Howorth wrote:
On Thu, 20 Jun 2019 22:26:02 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 20/06/2019 21.14, Dave Howorth wrote:
On Thu, 20 Jun 2019 18:50:03 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 20/06/2019 18.14, Dave Howorth wrote:
On Thu, 20 Jun 2019 17:55:53 +0200 Mathias Homann <Mathias.Homann@opensuse.org> wrote:
It's editor related - happens to me too, my $EDITOR and $VISUAL point at /usr/bin/joe
Yup.
$ sudo EDITOR=/usr/bin/jstar systemctl edit --system apache2 $ ls -la /etc/systemd/system/apache2.service.d/ total 8 drwxr-xr-x 1 root root 90 Jun 20 17:12 ./ drwxr-xr-x 1 root root 1622 Jun 20 15:31 ../ -rw-r--r-- 1 root root 27 Jun 20 17:12 override.conf -rw-r--r-- 1 root root 10 Jun 20 15:31 .#override.conf3934306d53707dd5~
So not new but definitely editor-related
Try another editor that creates backups. The problem will be there.
I already told you it wasn't; here's the proof:
$ sudo EDITOR=/usr/bin/vim systemctl edit --system apache2 $ ls -la /etc/systemd/system/apache2.service.d/ total 4 drwxr-xr-x 1 root root 26 Jun 20 20:02 ./ drwxr-xr-x 1 root root 1622 Jun 20 20:02 ../ -rw-r--r-- 1 root root 10 Jun 20 20:02 override.conf
and yes it was editing ...service.d/.#override.confb43e88ab28a12419
-rw-r--r-- 1 root root 10 Jun 20 20:02 .#override.confb43e88ab28a12419 -rw-r--r-- 1 root root 12288 Jun 20 20:03 .#override.confb43e88ab28a12419.swp
There are three solutions:
You missed out the obvious solution:
create the temporary file in place in the final directory (which serves to check that the directory is now present with adequate permissions) then rename it to the final name upon exit.
create the temporary file on a temporary directory, such as /tmp, edit then move to final destination. This is what what crontab does.
but there's no temporary file left in tmp when vim edits a crontab, just as there's no temporary file in the override directory when vim edits a service file
Make the call to the EDITOR in some manner that disables backups - but this will affect any other use of EDITOR by other calls.
Disable edit file backup altogether in joe - again, this affects other jobs.
The first one I think is better, and that lands it at systemd table.
The left over file is only present when you use jstar, not any other editor. So how is this systemd's fault?
I repeat: try any other editor that creates backup files by default.
You mean like vim does?
No, like joe does. Vim doesn't. cer@Telcontar:~/tmp/vim> l total 12 drwxr-xr-x 2 cer users 6 Jun 20 22:38 ./ drwxr-xr-x 113 cer users 8192 Jun 20 22:38 ../ cer@Telcontar:~/tmp/vim> vim cer@Telcontar:~/tmp/vim> vim p cer@Telcontar:~/tmp/vim> l total 16 drwxr-xr-x 2 cer users 15 Jun 20 22:39 ./ drwxr-xr-x 113 cer users 8192 Jun 20 22:38 ../ -rw-r--r-- 1 cer users 7 Jun 20 22:39 p cer@Telcontar:~/tmp/vim> vim p cer@Telcontar:~/tmp/vim> l total 16 drwxr-xr-x 2 cer users 15 Jun 20 22:39 ./ drwxr-xr-x 113 cer users 8192 Jun 20 22:38 ../ -rw-r--r-- 1 cer users 8 Jun 20 22:39 p cer@Telcontar:~/tmp/vim> See? vim doesn't. No p.bak file. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Carlos E. R. wrote:
I repeat: try any other editor that creates backup files by default.
You mean like vim does?
No, like joe does. Vim doesn't.
Given the right options, vim also creates a backup. See the "backup" and "writebackup" options. Afaict, the default is to write the backup, and delete it when you leave vim.
See? vim doesn't. No p.bak file.
vim backups are named filename~ (ie. with tilde appended). -- Per Jessen, Zürich (16.8°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 21/06/2019 08.38, Per Jessen wrote:
Carlos E. R. wrote:
I repeat: try any other editor that creates backup files by default.
You mean like vim does?
No, like joe does. Vim doesn't.
Given the right options, vim also creates a backup. See the "backup" and "writebackup" options. Afaict, the default is to write the backup, and delete it when you leave vim.
Well, joe creates a backup and leaves it there. What's the point of a deleted backup, if you decide to recover it hours later? Usually people find mistakes or change minds after exiting a program.
See? vim doesn't. No p.bak file.
vim backups are named filename~ (ie. with tilde appended).
Ok, same as jstar -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Carlos E. R. wrote:
On 21/06/2019 08.38, Per Jessen wrote:
Carlos E. R. wrote:
I repeat: try any other editor that creates backup files by default.
You mean like vim does?
No, like joe does. Vim doesn't.
Given the right options, vim also creates a backup. See the "backup" and "writebackup" options. Afaict, the default is to write the backup, and delete it when you leave vim.
Well, joe creates a backup and leaves it there.
You can make vim do that too. It's up to you. -- Per Jessen, Zürich (20.6°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Per Jessen <per@computer.org> [06-21-19 09:39]:
Carlos E. R. wrote:
On 21/06/2019 08.38, Per Jessen wrote:
Carlos E. R. wrote:
I repeat: try any other editor that creates backup files by default.
You mean like vim does?
No, like joe does. Vim doesn't.
Given the right options, vim also creates a backup. See the "backup" and "writebackup" options. Afaict, the default is to write the backup, and delete it when you leave vim.
Well, joe creates a backup and leaves it there.
You can make vim do that too. It's up to you.
he can also set joe to "-nobackup" but there is no one-fix-for-everything. but he can utilize joe's syntax file to make specific actions for particular file-types. if he cares. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 21/06/2019 17.58, Patrick Shanahan wrote:
* Per Jessen <per@computer.org> [06-21-19 09:39]:
Carlos E. R. wrote:
On 21/06/2019 08.38, Per Jessen wrote:
Carlos E. R. wrote:
> > I repeat: try any other editor that creates backup files by > default.
You mean like vim does?
No, like joe does. Vim doesn't.
Given the right options, vim also creates a backup. See the "backup" and "writebackup" options. Afaict, the default is to write the backup, and delete it when you leave vim.
Well, joe creates a backup and leaves it there.
You can make vim do that too. It's up to you.
he can also set joe to "-nobackup" but there is no one-fix-for-everything.
Not on the "EDITOR=..." enviroment variable, AFAIK.
but he can utilize joe's syntax file to make specific actions for particular file-types. if he cares.
Of course I care, but that would affect other uses of joe, not only systemd use of it. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [06-21-19 13:26]:
On 21/06/2019 17.58, Patrick Shanahan wrote:
* Per Jessen <per@computer.org> [06-21-19 09:39]:
Carlos E. R. wrote:
On 21/06/2019 08.38, Per Jessen wrote:
Carlos E. R. wrote:
>> >> I repeat: try any other editor that creates backup files by >> default. > > You mean like vim does?
No, like joe does. Vim doesn't.
Given the right options, vim also creates a backup. See the "backup" and "writebackup" options. Afaict, the default is to write the backup, and delete it when you leave vim.
Well, joe creates a backup and leaves it there.
You can make vim do that too. It's up to you.
he can also set joe to "-nobackup" but there is no one-fix-for-everything.
Not on the "EDITOR=..." enviroment variable, AFAIK.
but he can utilize joe's syntax file to make specific actions for particular file-types. if he cares.
Of course I care, but that would affect other uses of joe, not only systemd use of it.
then look into joe's syntax file -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 21/06/2019 22.30, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [06-21-19 13:26]:
On 21/06/2019 17.58, Patrick Shanahan wrote:
* Per Jessen <per@computer.org> [06-21-19 09:39]:
Carlos E. R. wrote:
On 21/06/2019 08.38, Per Jessen wrote:
Carlos E. R. wrote:
>>> >>> I repeat: try any other editor that creates backup files by >>> default. >> >> You mean like vim does? > > No, like joe does. Vim doesn't.
Given the right options, vim also creates a backup. See the "backup" and "writebackup" options. Afaict, the default is to write the backup, and delete it when you leave vim.
Well, joe creates a backup and leaves it there.
You can make vim do that too. It's up to you.
he can also set joe to "-nobackup" but there is no one-fix-for-everything.
Not on the "EDITOR=..." enviroment variable, AFAIK.
but he can utilize joe's syntax file to make specific actions for particular file-types. if he cares.
Of course I care, but that would affect other uses of joe, not only systemd use of it.
then look into joe's syntax file
No way. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [06-21-19 16:58]:
On 21/06/2019 22.30, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [06-21-19 13:26]:
On 21/06/2019 17.58, Patrick Shanahan wrote:
* Per Jessen <per@computer.org> [06-21-19 09:39]:
Carlos E. R. wrote:
On 21/06/2019 08.38, Per Jessen wrote: > Carlos E. R. wrote: > >>>> >>>> I repeat: try any other editor that creates backup files by >>>> default. >>> >>> You mean like vim does? >> >> No, like joe does. Vim doesn't. > > Given the right options, vim also creates a backup. See the "backup" > and "writebackup" options. Afaict, the default is to write the > backup, and delete it when you leave vim.
Well, joe creates a backup and leaves it there.
You can make vim do that too. It's up to you.
he can also set joe to "-nobackup" but there is no one-fix-for-everything.
Not on the "EDITOR=..." enviroment variable, AFAIK.
but he can utilize joe's syntax file to make specific actions for particular file-types. if he cares.
Of course I care, but that would affect other uses of joe, not only systemd use of it.
then look into joe's syntax file
No way.
then "Of course I care" is not so or not worth the concern. you could have just said that you didn't care and been done with it. actually most of the entire thread was wasted effort, since you *really* could not be bothered. .... -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 21/06/2019 23.04, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [06-21-19 16:58]:
On 21/06/2019 22.30, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [06-21-19 13:26]:
On 21/06/2019 17.58, Patrick Shanahan wrote:
* Per Jessen <per@computer.org> [06-21-19 09:39]:
Carlos E. R. wrote:
> On 21/06/2019 08.38, Per Jessen wrote: >> Carlos E. R. wrote: >> >>>>> >>>>> I repeat: try any other editor that creates backup files by >>>>> default. >>>> >>>> You mean like vim does? >>> >>> No, like joe does. Vim doesn't. >> >> Given the right options, vim also creates a backup. See the "backup" >> and "writebackup" options. Afaict, the default is to write the >> backup, and delete it when you leave vim. > > Well, joe creates a backup and leaves it there.
You can make vim do that too. It's up to you.
he can also set joe to "-nobackup" but there is no one-fix-for-everything.
Not on the "EDITOR=..." enviroment variable, AFAIK.
but he can utilize joe's syntax file to make specific actions for particular file-types. if he cares.
Of course I care, but that would affect other uses of joe, not only systemd use of it.
then look into joe's syntax file
No way.
then "Of course I care" is not so or not worth the concern. you could have just said that you didn't care and been done with it. actually most of the entire thread was wasted effort, since you *really* could not be bothered. ....
In your opinion. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
In data sabato 22 giugno 2019 00:14:15 CEST, Carlos E. R. ha scritto:
On 21/06/2019 23.04, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [06-21-19 16:58]:
On 21/06/2019 22.30, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [06-21-19 13:26]:
On 21/06/2019 17.58, Patrick Shanahan wrote:
* Per Jessen <per@computer.org> [06-21-19 09:39]: > Carlos E. R. wrote: >> On 21/06/2019 08.38, Per Jessen wrote: >>> Carlos E. R. wrote: >>>>>> I repeat: try any other editor that creates backup files by >>>>>> default. >>>>> >>>>> You mean like vim does? >>>> >>>> No, like joe does. Vim doesn't. >>> >>> Given the right options, vim also creates a backup. See the >>> "backup" >>> and "writebackup" options. Afaict, the default is to write the >>> backup, and delete it when you leave vim. >> >> Well, joe creates a backup and leaves it there. > > You can make vim do that too. It's up to you.
he can also set joe to "-nobackup" but there is no one-fix-for-everything.
Not on the "EDITOR=..." enviroment variable, AFAIK.
but he can utilize joe's syntax file to make specific actions for particular file-types. if he cares.
Of course I care, but that would affect other uses of joe, not only systemd use of it.
then look into joe's syntax file
No way.
then "Of course I care" is not so or not worth the concern. you could have just said that you didn't care and been done with it. actually most of the entire thread was wasted effort, since you *really* could not be bothered. ....
In your opinion. Carlos, I have been bothered by the same problem and resolved by putting a timeout of 200 for spamd in my system. As this is AFAIU a thing about how to do it best, I share my thing which is doing editing amavis via nano. As the system is running systemd: first of all I went root with
$ su - then I entered # systemctl edit --full spamd.service which opens nano in order to edit /etc/systemd/system/ in the section [service] you join the value: TimeoutStartSec=200 I am sure you can experiment to lower that value, but with 200 I am fine and did not experience problems. You save with Ctrl + X and are asked whether you want to save the value via a spamd.service.nnnn file were nnnn stands for any systemgiven number. This creates in /etc/systemd/system reliably the file spamd.service file that contains the desired timeout value for spamd daemonized verson. It should survive any normal system upgrade AFAIK and that way one does not mess up systemd settings. Probably that was trivial for you, but as I did follow superficially the thread, at the end I did not understand if you solved. Greetings. _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postf�cher sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
stakanov wrote:
but as I did follow superficially the thread, at the end I did not understand if you solved.
The original problem was mine and it was solved. It was a simple configuration issue. The vanilla systemd unit has "type=forking", but in my setup, spamd does not fork so I needed "type=simple". -- Per Jessen, Zürich (26.4°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/07/2019 06.19, stakanov wrote:
In data sabato 22 giugno 2019 00:14:15 CEST, Carlos E. R. ha scritto:
Carlos, I have been bothered by the same problem and resolved by putting a timeout of 200 for spamd in my system. As this is AFAIU a thing about how to do it best, I share my thing which is doing editing amavis via nano. As the system is running systemd: first of all I went root with
$ su -
then I entered
# systemctl edit --full spamd.service
which opens nano in order to edit
/etc/systemd/system/
in the section [service] you join the value: TimeoutStartSec=200
I am sure you can experiment to lower that value, but with 200 I am fine and did not experience problems. You save with Ctrl + X and are asked whether you want to save the value via a spamd.service.nnnn file were nnnn stands for any systemgiven number. This creates in /etc/systemd/system reliably the file spamd.service file that contains the desired timeout value for spamd daemonized verson. It should survive any normal system upgrade AFAIK and that way one does not mess up systemd settings.
Probably that was trivial for you, but as I did follow superficially the thread, at the end I did not understand if you solved.
Yes, I solved it, earlier than this thread. Initially I edited the main configuration file, and then here I found out that we could do it for this service only, so that a an override file would do. And then Mathias Homann told us about the edit command in systemd: systemctl edit spamd.service Using "--full" I don't think is appropriate, because if there is an update to the service you will miss it. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 06/07/2019 06.19, stakanov wrote:
In data sabato 22 giugno 2019 00:14:15 CEST, Carlos E. R. ha scritto:
Carlos, I have been bothered by the same problem and resolved by putting a timeout of 200 for spamd in my system. As this is AFAIU a thing about how to do it best, I share my thing which is doing editing amavis via nano. As the system is running systemd: first of all I went root with
$ su -
then I entered
# systemctl edit --full spamd.service
which opens nano in order to edit
/etc/systemd/system/
in the section [service] you join the value: TimeoutStartSec=200
I am sure you can experiment to lower that value, but with 200 I am fine and did not experience problems. You save with Ctrl + X and are asked whether you want to save the value via a spamd.service.nnnn file were nnnn stands for any systemgiven number. This creates in /etc/systemd/system reliably the file spamd.service file that contains the desired timeout value for spamd daemonized verson. It should survive any normal system upgrade AFAIK and that way one does not mess up systemd settings.
Probably that was trivial for you, but as I did follow superficially the thread, at the end I did not understand if you solved.
Yes, I solved it, earlier than this thread. Initially I edited the main configuration file, and then here I found out that we could do it for this service only, so that a an override file would do. And then Mathias Homann told us about the edit command in systemd:
systemctl edit spamd.service
Using "--full" I don't think is appropriate, because if there is an update to the service you will miss it. Thank you for the heads up. Sorry for the noise, a side effect of mailing
In data sabato 6 luglio 2019 14:52:54 CEST, Carlos E. R. ha scritto: lists is the blurring of information. So I should use the command without "--full" if I well understand? Thank you. _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postf�cher sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/07/2019 22.54, stakanov wrote:
In data sabato 6 luglio 2019 14:52:54 CEST, Carlos E. R. ha scritto:
systemctl edit spamd.service
Using "--full" I don't think is appropriate, because if there is an update to the service you will miss it. Thank you for the heads up. Sorry for the noise, a side effect of mailing lists is the blurring of information. So I should use the command without "--full" if I well understand? Thank you.
You can use any, depends on the intention. This time, without "--full" is better. With "--full", you replace the entire original service file. Which is an interesting trick of systemd. Nothing like that on initd ;-) -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
participants (8)
-
Carlos E. R. -
Carlos E.R. -
Dave Howorth -
Mathias Homann -
Patrick Shanahan -
Per Jessen -
stakanov -
Yamaban