rvice file) can coexist. It's just a suggestion.
On Fri, Jul 8, 2016 at 7:16 PM, Lennart Poettering
wrote:
> On Fri, 08.07.16 16:35, One Infinite Loop (6po...@gmail.com) wrote:
>
> > A few usecases:
> > 1) I want to delete specific files once a day
>
> For this you
:03, One Infinite Loop (6po...@gmail.com) wrote:
>
> > If you want to disable timer alone or do something else, then you could
> use
> > .timer file. If not, instead of [Install] section in .service file, you
> > could have a [Timer] section.
>
> The reason timer de
pics:
>
>1. Re: Adding a Timer section to .service files (Reindl Harald)
>2. Re: Adding a Timer section to .service files (Michał Zegan)
>3. Re: Adding a Timer section to .service files (Mantas Mikulėnas)
>4. Re: Adding a Timer section to .service files (Tomasz Torcz
'/usr/bin/renice -15 -p
$(/usr/bin/pgrep -f /opt/google/chrome/chrome)'` every 15 seconds, for
example.
On Fri, Jul 8, 2016 at 5:06 PM, Mantas Mikulėnas wrote:
> On Fri, Jul 8, 2016 at 4:35 PM, One Infinite Loop <6po...@gmail.com>
> wrote:
>
>> A few usecases:
>
OK, I have a new idea: let's not call the section [Timer] but [Crontab].
Of course, the manual page will explain what is its purpose. I expect
feedback.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mail
A few usecases:
1) I want to delete specific files once a day
2)I want to free RAM using sync command and `echo 3 >
/proc/sys/vm/drop_caches` every 15 seconds
3)I want to make sure certain processes always run using a specific nice
value like -15. I know control groups are invented but it's not the
Why would you create another one? Why are there always people who try to
complicate things?
The same way you read and edit your sudoers files, your fstab file, you
will read & edit the .service file that your distro is shipping to you.
Let's not forget about the manual page that will document the c
There are cases when you don't need .timer files but only a [Timer]
section. With a well written manual page, systemd users will understand why
is useful to have a [Timer] section inside a .service file.
___
systemd-devel mailing list
systemd-devel@lists.
If you want to disable timer alone or do something else, then you could use
.timer file. If not, instead of [Install] section in .service file, you
could have a [Timer] section.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://
systemctl start foo.service
systemctl enable foo.service
systemd tools must be modified/adjusted too
On Fri, Jul 8, 2016 at 8:08 AM, Mantas Mikulėnas wrote:
> On Fri, Jul 8, 2016 at 7:52 AM, One Infinite Loop <6po...@gmail.com>
> wrote:
>
>> Instead of having a .service f
Instead of having a .service file and a .timer file why not having a
[Timer] section inside a .service file? It would be much more manageable as
one file.
Of course, if there are users who prefer having .timer files, .timer files
will continue to exist.
I use systemd 229.
It would be great if I could empty directories (creating a .conf file
in /etc/tmpfiles.d) but not at boot time, but before shutting
down/rebooting the pc. I am using systemd 229. Thanks in advance.
___
systemd-devel mailing list
systemd-devel@lists.freede
12 matches
Mail list logo
