[15.5] systemd timer ignores override/config edit
7 days ago I ran 'systemctl cat mdcheck_start.timer' and decided I didn't like either the time or the day of the default, Sunday @01:00, so I did 'systemctl edit mdcheck_start.timer'. The following is the result of saving the edit: # systemctl cat mdcheck_start.timer # /usr/lib/systemd/system/mdcheck_start.timer # This file is part of mdadm. # # mdadm is free software; you can redistribute it and/or modify it # under the terms of the GNU General Public License as published by # the Free Software Foundation; either version 2 of the License, or # (at your option) any later version. [Unit] Description=MD array scrubbing [Timer] OnCalendar=Sun *-*-* 1:00:00 [Install] WantedBy= mdmonitor.service Also= mdcheck_continue.timer # /etc/systemd/system/mdcheck_start.timer.d/override.conf OnCalendar=Sat *-*-* 4:00:00 # The override file created by the edit contains only: OnCalendar=Sat *-*-* 4:00:00 I didn't change any file directly. I added that 04:00 Saturday line in between the marks indicated by opening the systemd object for edit, about 4 lines from top in the blank space. I rebooted twice since. It's 2:20 Saturday as I type this, and mdcheck is running, started by the timer at 01:00. 'systemctl status mdcheck_start.timer' reports: ... systemd[1]: /etc/systemd/system/mdcheck_start.timer.d/override.conf:1: Assignment outside of section. Ignoring ... What more is required to implement my timer change here? As yet, I haven't found an example of making a change to a unit file, rather than an addition or deletion. :( The editor systemctl uses for editing is not my preference. I think it's nano. I want mcedit. Where do I change the global default editor to my preference? Nothing looks obvious in /etc/sysconfig/, in yast or in /etc/alternatives/. If there's no simple way, and the /etc/alternatives method can be implemented, I'd like to try it. I attempted so based on https://unix.stackexchange.com/questions/408413/change-default-editor-to-vim... but failed due to 'which editor' returning not found. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 14.01.2024 11:02, Felix Miata wrote:
7 days ago I ran 'systemctl cat mdcheck_start.timer' and decided I didn't like either the time or the day of the default, Sunday @01:00, so I did 'systemctl edit mdcheck_start.timer'. The following is the result of saving the edit: # systemctl cat mdcheck_start.timer # /usr/lib/systemd/system/mdcheck_start.timer # This file is part of mdadm. # # mdadm is free software; you can redistribute it and/or modify it # under the terms of the GNU General Public License as published by # the Free Software Foundation; either version 2 of the License, or # (at your option) any later version.
[Unit] Description=MD array scrubbing
[Timer] OnCalendar=Sun *-*-* 1:00:00
[Install] WantedBy= mdmonitor.service Also= mdcheck_continue.timer
# /etc/systemd/system/mdcheck_start.timer.d/override.conf OnCalendar=Sat *-*-* 4:00:00 # The override file created by the edit contains only:
OnCalendar=Sat *-*-* 4:00:00
I didn't change any file directly. I added that 04:00 Saturday line in between the marks indicated by opening the systemd object for edit, about 4 lines from top in the blank space.
I rebooted twice since. It's 2:20 Saturday as I type this, and mdcheck is running, started by the timer at 01:00. 'systemctl status mdcheck_start.timer' reports: ... systemd[1]: /etc/systemd/system/mdcheck_start.timer.d/override.conf:1: Assignment outside of section. Ignoring ... What more is required to implement my timer change here? As yet, I haven't found an example of making a change to a unit file, rather than an addition or deletion. :(
I wonder, whether you ever try to read documentation before asking. What is not clear in May be specified more than once, in which case the timer unit will trigger whenever any of the specified expressions elapse. Moreover calendar timers and monotonic timers (see above) may be combined within the same timer unit. If the empty string is assigned to any of these options, the list of timers is reset (both OnCalendar= timers and monotonic timers, see above), and all prior assignments will have no effect.
The editor systemctl uses for editing is not my preference. I think it's nano. I want mcedit. Where do I change the global default editor to my preference? Nothing looks obvious in /etc/sysconfig/, in yast or in /etc/alternatives/. If there's no simple way, and the /etc/alternatives method can be implemented, I'd like to try it. I attempted so based on https://unix.stackexchange.com/questions/408413/change-default-editor-to-vim... but failed due to 'which editor' returning not found.
Andrei Borzenkov composed on 2024-01-14 11:27 (UTC+0300):
What is not clear in
May be specified more than once, in which case the timer unit will trigger whenever any of the specified expressions elapse. Moreover calendar timers and monotonic timers (see above) may be combined within the same timer unit.
If the empty string is assigned to any of these options, the list of timers is reset (both OnCalendar= timers and monotonic timers, see above), and all prior assignments will have no effect.
What doc is this scrambled paste from? May be specified more than once, in which case the timer unit will trigger whenever any of the specified expressions elapse. Moreover calendar timers and monotonic timers (see above) may be combined within the same timer unit. If the empty string is assigned to any of these options, the list of timers is reset (both OnCalendar= timers and monotonic timers, see above), and all prior assignments will have no effect. Even unscrambled, for all practical purposes, all of it is unclear, since none of it seems relevant to the issue of drop-in editing. Documentation absent examples to me is commonly useless. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On Sun, 14 Jan 2024 03:02:30 -0500, Felix Miata
The editor systemctl uses for editing is not my preference. I think it's nano. I want mcedit. Where do I change the global default editor to my preference? Nothing looks obvious in /etc/sysconfig/, in yast or in /etc/alternatives/. If there's no simple way, and the /etc/alternatives method can be implemented, I'd like to try it. I attempted so based on https://unix.stackexchange.com/questions/408413/change-default-editor-to-vim... but failed due to 'which editor' returning not found.
Add 'export EDITOR=/usr/bin/mcedit' to /root/.profile . If you want it only for systemctl, use 'export SYSTEMD_EDITOR=/usr/bin/mcedit' instead. -- Robert Webb
On 1/14/24 09:02, Felix Miata wrote:
7 days ago I ran 'systemctl cat mdcheck_start.timer' and decided I didn't like either the time or the day of the default, Sunday @01:00, so I did 'systemctl edit mdcheck_start.timer'. The following is the result of saving the edit: # systemctl cat mdcheck_start.timer # /usr/lib/systemd/system/mdcheck_start.timer # This file is part of mdadm. # # mdadm is free software; you can redistribute it and/or modify it # under the terms of the GNU General Public License as published by # the Free Software Foundation; either version 2 of the License, or # (at your option) any later version.
[Unit] Description=MD array scrubbing
[Timer] OnCalendar=Sun *-*-* 1:00:00
[Install] WantedBy= mdmonitor.service Also= mdcheck_continue.timer
# /etc/systemd/system/mdcheck_start.timer.d/override.conf OnCalendar=Sat *-*-* 4:00:00 # The override file created by the edit contains only:
OnCalendar=Sat *-*-* 4:00:00
Hi, two issues in your drop-in file: you need to specify the section headers, and you need to clear the existing entry (assuming you don't want two calendar entries). For example: ``` [Timer] OnCalendar= OnCalendar=Sat *-*-* 4:00:00 ``` Hope that helps. Georg
I didn't change any file directly. I added that 04:00 Saturday line in between the marks indicated by opening the systemd object for edit, about 4 lines from top in the blank space.
I rebooted twice since. It's 2:20 Saturday as I type this, and mdcheck is running, started by the timer at 01:00. 'systemctl status mdcheck_start.timer' reports: ... systemd[1]: /etc/systemd/system/mdcheck_start.timer.d/override.conf:1: Assignment outside of section. Ignoring ... What more is required to implement my timer change here? As yet, I haven't found an example of making a change to a unit file, rather than an addition or deletion. :(
The editor systemctl uses for editing is not my preference. I think it's nano. I want mcedit. Where do I change the global default editor to my preference? Nothing looks obvious in /etc/sysconfig/, in yast or in /etc/alternatives/. If there's no simple way, and the /etc/alternatives method can be implemented, I'd like to try it. I attempted so based on https://unix.stackexchange.com/questions/408413/change-default-editor-to-vim... but failed due to 'which editor' returning not found.
Georg Pfuetzenreuter composed on 2024-01-14 11:34 (UTC+0100):
Felix Miata wrote:
7 days ago I ran 'systemctl cat mdcheck_start.timer' and decided I didn't like either the time or the day of the default, Sunday @01:00, so I did 'systemctl edit mdcheck_start.timer'. The following is the result of saving the edit: # systemctl cat mdcheck_start.timer # /usr/lib/systemd/system/mdcheck_start.timer # This file is part of mdadm.
# mdadm is free software; you can redistribute it and/or modify it # under the terms of the GNU General Public License as published by # the Free Software Foundation; either version 2 of the License, or # (at your option) any later version.
[Unit] Description=MD array scrubbing
[Timer] OnCalendar=Sun *-*-* 1:00:00
[Install] WantedBy= mdmonitor.service Also= mdcheck_continue.timer
# /etc/systemd/system/mdcheck_start.timer.d/override.conf OnCalendar=Sat *-*-* 4:00:00 # The override file created by the edit contains only:
OnCalendar=Sat *-*-* 4:00:00
two issues in your drop-in file: you need to specify the section headers, and you need to clear the existing entry (assuming you don't want two calendar entries). For example:
``` [Timer] OnCalendar= OnCalendar=Sat *-*-* 4:00:00 ```
Hope that helps.
It apparently did, but...
started by the timer at 01:00. 'systemctl status mdcheck_start.timer' reports: ... systemd[1]: /etc/systemd/system/mdcheck_start.timer.d/override.conf:1: Assignment outside of section. Ignoring
After systemctl cat mdcheck_start.timer looked right and I ran systemctl daemon-reload, systemctl status mdcheck_start.timer continued producing the same error message quoted above. systemctl status mdcheck_start.timer only showed the change effective after a reboot. So now: # systemctl status mdcheck_start.timer ● mdcheck_start.timer - MD array scrubbing Loaded: loaded (/usr/lib/systemd/system/mdcheck_start.timer; enabled; vendor preset: enabled) Drop-In: /etc/systemd/system/mdcheck_start.timer.d └─override.conf Active: active (waiting) since Mon 2024-01-15 01:00:53 EST; 2min 11s ago Trigger: Sat 2024-01-20 04:00:00 EST; 5 days left Triggers: ● mdcheck_start.service Jan 15 01:00:53 00srv systemd[1]: Started MD array scrubbing. # What causes the scrubbing? # systemctl list-unit-files | grep scrub 00srv:~ # journalctl -b -1 | grep scrub Jan 08 21:03:21 00srv systemd[1]: Started MD array scrubbing - continuation. Jan 08 21:03:21 00srv systemd[1]: Started MD array scrubbing. Jan 09 01:05:11 00srv systemd[1]: Condition check resulted in MD array scrubbing - continuation being skipped. Jan 10 01:05:11 00srv systemd[1]: Condition check resulted in MD array scrubbing - continuation being skipped. Jan 11 01:05:11 00srv systemd[1]: Condition check resulted in MD array scrubbing - continuation being skipped. Jan 12 01:05:11 00srv systemd[1]: Condition check resulted in MD array scrubbing - continuation being skipped. Jan 13 01:05:11 00srv systemd[1]: Condition check resulted in MD array scrubbing - continuation being skipped. Jan 14 01:00:11 00srv systemd[1]: Starting MD array scrubbing... Jan 14 01:05:00 00srv systemd[1]: Starting MD array scrubbing - continuation... Jan 14 01:05:00 00srv systemd[1]: Finished MD array scrubbing - continuation. Jan 14 03:32:15 00srv systemd[1]: Finished MD array scrubbing. Jan 15 01:00:18 00srv systemd[1]: Stopped MD array scrubbing - continuation. Jan 15 01:00:18 00srv systemd[1]: Stopped MD array scrubbing. # -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 2024-01-15 01:01, Felix Miata wrote:
Georg Pfuetzenreuter composed on 2024-01-14 11:34 (UTC+0100):
``` [Timer] OnCalendar= OnCalendar=Sat *-*-* 4:00:00 ```
Hope that helps.
It apparently did, but...
started by the timer at 01:00. 'systemctl status mdcheck_start.timer' reports: ... systemd[1]: /etc/systemd/system/mdcheck_start.timer.d/override.conf:1: Assignment outside of section. Ignoring
After systemctl cat mdcheck_start.timer looked right and I ran systemctl daemon-reload, systemctl status mdcheck_start.timer continued producing the same error message quoted above. systemctl status mdcheck_start.timer only showed the change effective after a reboot. So now:
If all else fails, executing "systemctl stop ..." followed by "systemctl start ..." will set things right
On 2024-01-14 02:02, Felix Miata wrote:
7 days ago I ran 'systemctl cat mdcheck_start.timer' and decided I didn't like either the time or the day of the default, Sunday @01:00, so I did 'systemctl edit mdcheck_start.timer'. The following is the result of saving the edit: # systemctl cat mdcheck_start.timer # /usr/lib/systemd/system/mdcheck_start.timer # This file is part of mdadm. # # mdadm is free software; you can redistribute it and/or modify it # under the terms of the GNU General Public License as published by # the Free Software Foundation; either version 2 of the License, or # (at your option) any later version.
[Unit] Description=MD array scrubbing
[Timer] OnCalendar=Sun *-*-* 1:00:00
[Install] WantedBy= mdmonitor.service Also= mdcheck_continue.timer
# /etc/systemd/system/mdcheck_start.timer.d/override.conf OnCalendar=Sat *-*-* 4:00:00 # The override file created by the edit contains only:
OnCalendar=Sat *-*-* 4:00:00
I didn't change any file directly. I added that 04:00 Saturday line in between the marks indicated by opening the systemd object for edit, about 4 lines from top in the blank space. This is totally confusing. Where exactly did you put that line you want to add? It should have been placed under the [Timer] title; above or below the existing line should not matter. Try deleting the existing override.conf file, and editing the service file again, this time placing your new line in the proper place. Then run"systemctl cat mdcheck_start.timer" again to make sure the override.conf file contains all the original lines, plus the new one.
I rebooted twice since. It's 2:20 Saturday as I type this, and mdcheck is running, started by the timer at 01:00. 'systemctl status mdcheck_start.timer' reports: ... systemd[1]: /etc/systemd/system/mdcheck_start.timer.d/override.conf:1: Assignment outside of section. Ignoring ... What more is required to implement my timer change here? As yet, I haven't found an example of making a change to a unit file, rather than an addition or deletion. :(
The editor systemctl uses for editing is not my preference. I think it's nano. I want mcedit. Where do I change the global default editor to my preference? Nothing looks obvious in /etc/sysconfig/, in yast or in /etc/alternatives/. If there's no simple way, and the /etc/alternatives method can be implemented, I'd like to try it. I attempted so based on https://unix.stackexchange.com/questions/408413/change-default-editor-to-vim... but failed due to 'which editor' returning not found.
In SUSE, there is no "editor"; it is "edit" instead, which (at least on my system) points to vim (but I don't have mc installed, so who knows?). So, proceed as Robert Webb suggests, which is just what is posted in that URL, except with mcedit instead of vim.
On 2024-01-14 12:10, Darryl Gregorash wrote:
On 2024-01-14 02:02, Felix Miata wrote:
The following is the result of saving the edit: # systemctl cat mdcheck_start.timer # /usr/lib/systemd/system/mdcheck_start.timer # This file is part of mdadm. # # mdadm is free software; you can redistribute it and/or modify it # under the terms of the GNU General Public License as published by # the Free Software Foundation; either version 2 of the License, or # (at your option) any later version.
[Unit] Description=MD array scrubbing
[Timer] OnCalendar=Sun *-*-* 1:00:00
[Install] WantedBy= mdmonitor.service Also= mdcheck_continue.timer
# /etc/systemd/system/mdcheck_start.timer.d/override.conf OnCalendar=Sat *-*-* 4:00:00 # The override file created by the edit contains only:
OnCalendar=Sat *-*-* 4:00:00
I didn't change any file directly. I added that 04:00 Saturday line in between the marks indicated by opening the systemd object for edit, about 4 lines from top in the blank space. This is totally confusing. Where exactly did you put that line you want to add?
It is not confusing. The pasted text is the direct result of running the command: systemctl cat mdcheck_start.timer and it outputs two files, the system one and the override file. The system file is not edited, there is a an override file with a single text line with the "edit".
It should have been placed under the [Timer] title; above or below the existing line should not matter. Try deleting the existing override.conf file, and editing the service file again, this time placing your new line in the proper place.
NO! That breaks things, specially with updates. The correct method is what Georg Pfuetzenreuter suggested. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 2024-01-14 12:10, Darryl Gregorash wrote:
On 2024-01-14 02:02, Felix Miata wrote:
The following is the result of saving the edit: # systemctl cat mdcheck_start.timer # /usr/lib/systemd/system/mdcheck_start.timer # This file is part of mdadm. # # mdadm is free software; you can redistribute it and/or modify it # under the terms of the GNU General Public License as published by # the Free Software Foundation; either version 2 of the License, or # (at your option) any later version.
[Unit] Description=MD array scrubbing
[Timer] OnCalendar=Sun *-*-* 1:00:00
[Install] WantedBy= mdmonitor.service Also= mdcheck_continue.timer
# /etc/systemd/system/mdcheck_start.timer.d/override.conf OnCalendar=Sat *-*-* 4:00:00 # The override file created by the edit contains only:
OnCalendar=Sat *-*-* 4:00:00
I didn't change any file directly. I added that 04:00 Saturday line in between the marks indicated by opening the systemd object for edit, about 4 lines from top in the blank space. This is totally confusing. Where exactly did you put that line you want to add?
It is not confusing. The pasted text is the direct result of running the command:
systemctl cat mdcheck_start.timer
and it outputs two files, the system one and the override file. The system file is not edited, there is a an override file with a single text line with the "edit". Well, duuh, Carlos. Read closely and you'll see I'm not even talking about that. What I'm asking about is just where did he place the new
On 2024-01-14 05:59, Carlos E. R. wrote: line in the service file.
It should have been placed under the [Timer] title; above or below the existing line should not matter. Try deleting the existing override.conf file, and editing the service file again, this time placing your new line in the proper place.
NO!
That breaks things, specially with updates.
Wrong, wrong, couldn't be more wrong. When you execute "systemctl edit", the original file is left unchanged (which you should have noticed in the output of the systemctl cat command). The modified file is saved as: /etc/systemd/system/<service>.d/override.conf Yes, systemd is smart enough to know when a service file has been modified, so it runs the override file instead of the original. And no, the override file is *NOT* modified in any way during an update. AFAIK at this time, the only way to get rid of it is to physically delete it. If you still want to dispute any of this, I will post the results for my boinc-client service file for you to peruse.
The correct method is what Georg Pfuetzenreuter suggested.
Isn't that precisely what I said when I wrote this?
It should have been placed under the [Timer] title; above or below the existing line should not matter.
On 2024-01-14 13:58, Darryl Gregorash wrote:
On 2024-01-14 05:59, Carlos E. R. wrote:
On 2024-01-14 12:10, Darryl Gregorash wrote:
On 2024-01-14 02:02, Felix Miata wrote:
This is totally confusing. Where exactly did you put that line you want to add?
It is not confusing. The pasted text is the direct result of running the command:
systemctl cat mdcheck_start.timer
and it outputs two files, the system one and the override file. The system file is not edited, there is a an override file with a single text line with the "edit". Well, duuh, Carlos. Read closely and you'll see I'm not even talking about that. What I'm asking about is just where did he place the new line in the service file.
It is absolutely clear. It has no section line, so there is a syntax error, which probably systemctl should have caught and warned about.
It should have been placed under the [Timer] title; above or below the existing line should not matter. Try deleting the existing override.conf file, and editing the service file again, this time placing your new line in the proper place.
NO!
That breaks things, specially with updates.
Wrong, wrong, couldn't be more wrong.
Sorry, I thought you had said to delete the service file, while you said to delete the override file. But that one is also wrong. He only needs to run 'systemctl edit mdcheck_start.timer' and edit the file, which will be: OnCalendar=Sat *-*-* 4:00:00 to [Timer] OnCalendar=Sat *-*-* 4:00:00 and save. It is an editor, no need to delete the override file manually. Still, the file would not work as intended, so edit again to: [Timer] OnCalendar= OnCalendar=Sat *-*-* 4:00:00
When you execute "systemctl edit", the original file is left unchanged (which you should have noticed in the output of the systemctl cat command). The modified file is saved as: /etc/systemd/system/<service>.d/override.conf
I know that. ...
The correct method is what Georg Pfuetzenreuter suggested.
Isn't that precisely what I said when I wrote this?
It should have been placed under the [Timer] title; above or below the existing line should not matter.
-- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 2024-01-14 12:15, Carlos E. R. wrote:
On 2024-01-14 13:58, Darryl Gregorash wrote:
On 2024-01-14 05:59, Carlos E. R. wrote:
On 2024-01-14 12:10, Darryl Gregorash wrote:
On 2024-01-14 02:02, Felix Miata wrote:
This is totally confusing. Where exactly did you put that line you want to add?
It is not confusing. The pasted text is the direct result of running the command:
systemctl cat mdcheck_start.timer
and it outputs two files, the system one and the override file. The system file is not edited, there is a an override file with a single text line with the "edit". Well, duuh, Carlos. Read closely and you'll see I'm not even talking about that. What I'm asking about is just where did he place the new line in the service file.
It is absolutely clear. It has no section line, so there is a syntax error, which probably systemctl should have caught and warned about. This is exactly what I spoke about in the next part below:
It should have been placed under the [Timer] title; above or below the existing line should not matter.
But I wasn't speaking about what was wrong here, I was saying it was quite unclear where he had put the new line in the first place. This is why I asked where exactly he put the line, right after I said what he wrote was rather confusing.
Sorry, I thought you had said to delete the service file, while you said to delete the override file. But that one is also wrong. He only needs to run 'systemctl edit mdcheck_start.timer' and edit the file, which I have usually found it best to revert the system to its previous state before making further edits to the configuration. This prevents one from compounding the error by changing an erroneous line or phrase into something that is even worse. I just discovered the systemctl way to achieve this: systemctl revert <service>
[Timer] OnCalendar=Sat *-*-* 4:00:00
and save. It is an editor, no need to delete the override file manually. Still, the file would not work as intended, so edit again to:
[Timer] OnCalendar= OnCalendar=Sat *-*-* 4:00:00 I'm not sure of the rationale for this. The first line clears out all
I bet it just deletes the override file (oh, and surely restarts the service as well). Note also that both the edit and revert commands cause the service file to be reloaded before systemctl exits. previous timers, which will be accomplished by simply restarting the service.
Darryl Gregorash composed on 2024-01-14 14:34 (UTC-0600):
Carlos E. R. wrote:
It is an editor, no need to delete the override file manually. Still, the file would not work as intended, so edit again to:
[Timer] OnCalendar= OnCalendar=Sat *-*-* 4:00:00
I'm not sure of the rationale for this. The first line clears out all previous timers, which will be accomplished by simply restarting the service.
I find the two lines above the match to my original edit line (OnCalendar=Sat *-*-* 4:00:00) totally unintuitive. I would expect anything on a line preceding an "=" in the editing head to replace its match in the original below, with no other changes needed. Anything more, including a header, would constitute an addition, not a modification (aka edit or change). -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
Darryl Gregorash composed on 2024-01-14 14:34 (UTC-0600):
Carlos E. R. wrote:
It is an editor, no need to delete the override file manually. Still, the file would not work as intended, so edit again to:
[Timer] OnCalendar= OnCalendar=Sat *-*-* 4:00:00
I'm not sure of the rationale for this. The first line clears out all previous timers, which will be accomplished by simply restarting the service.
I find the two lines above the match to my original edit line (OnCalendar=Sat *-*-* 4:00:00) totally unintuitive. I would expect anything on a line preceding an "=" in the editing head to replace its match in the original below, with no other changes needed. Anything more, including a header, would constitute an addition, not a modification (aka edit or change). I sympathize with you. The systemd man pages and all related man pages are about as clear as mud. When I found it necessary to make changes to my boinc-client service file, I was able to find a good document that clearly described everything. Unfortunately, I seem to have forgotten to bookmark it, and I don't remember what search terms I used when I found it. It is clear that editing a service file is not as simple as things used to be under SystemV. With systemd, everything needs to be part of a
On 2024-01-14 14:58, Felix Miata wrote: section headed by a specific title, as above. One can no longer simply drop a new line anywhere and expect it to work. I'll keep looking for that documentation that I used previously, and when I find it again (hopefully soon), I'll post it in here so everyone will be able to use it. Wish me luck :D ! Meanwhile, if in doubt, all I can suggest is that you just ask first in here, and I'm sure someone will be able to give you a clear explanation.
participants (6)
-
Andrei Borzenkov -
Carlos E. R. -
Darryl Gregorash -
Felix Miata -
Georg Pfuetzenreuter -
Robert Webb