On Thu, Jul 12, 2018 at 2:06 PM Matt Zagrabelny wrote:
> On Thu, Jul 12, 2018 at 3:07 PM, Filipe Brandenburger
> wrote:
>> Take a look at systemd-run and, in particular, options such as
>> --on-active=, --on-calendar= and --timer-property=, which allow you to
>> set a .timer option on demand
Hey Filipe,
On Thu, Jul 12, 2018 at 3:07 PM, Filipe Brandenburger wrote:
> Hi,
>
> On Thu, Jul 12, 2018 at 12:04 PM Matt Zagrabelny
> wrote:
> > I know systemd can replace cron. Do folks use it to replace "at", too?
> >
> > I know it *can* - with two files per "at" entry and then enabling and
Hi,
On Thu, Jul 12, 2018 at 12:04 PM Matt Zagrabelny wrote:
> I know systemd can replace cron. Do folks use it to replace "at", too?
>
> I know it *can* - with two files per "at" entry and then enabling and
> starting the timer.
>
> Is there an easier with to replace "at" with systemd than
I know systemd can replace cron. Do folks use it to replace "at", too?
I know it *can* - with two files per "at" entry and then enabling and
starting the timer.
Is there an easier with to replace "at" with systemd than creating two
files and enabling and starting the timer?
Thanks for any info!
Dear systemd folks,
Trying to decrease the start-up time, I noticed that `systemd-logind`
probes devices in serial(?) (instead of parallel).
From `manager_enumerate_buttons(Manager *m)` in `src/login/logind.c`:
```
udev_list_entry_foreach(item, first) {
Hi Chris.
On 07/11/2018 09:44 PM, Chris Murphy wrote:
> Somehow journald would not
> delete its own files until I had deleted a few manually.
Indeed, see man page update [1] added recently for more details. I
assume your space was occupied by active journal files. Do you have any
detailed break
On Wed, Jul 11, 2018 at 06:52:12PM -0700, Filipe Brandenburger wrote:
> Hey Daniel!
>
> On Wed, Jul 11, 2018 at 5:16 PM Daniel Wang wrote:
> > I have a unit, say foo.service, on my system that's in
> > /usr/lib/systemd/system, but disabled by preset.
>
> Not that it matters, but presets don't
