Hi,
I'm playing with mount units as a replacement of traditional fstab
declaration as I'd like to use some systemd facilities, for example
requirements between services and their underlying storage.
The systemd.mount(5) manual says:
If the mount point is not existing at time of mounting, it
Zitat von Frederic Crozat fcro...@suse.com:
Le mardi 01 novembre 2011 à 23:53 +0100, Lennart Poettering a écrit :
On Mon, 17.10.11 17:28, Tom Gundersen (t...@jklm.no) wrote:
Yes, you are right. And I have no idea how we should fix that in a
pretty way. Thankfully not many folks are using
On Thu, Jan 5, 2012 at 12:36 PM, Thomas Meyer tho...@m3y3r.de wrote:
any news on this? I see this error on Fedoar 16, too.
I posted a patch that should fix the problem, but I don't know if
anyone tried it (so testing would be welcome):
I'm having trouble getting my head round how hotplugged device
activation should work with systemctl enable/disable.
I have a udev rule that uses ENV{SYSTEMD_WANTS}=foo@%k.service to hook
device hotplug to systemd and a template unit file for foo@.service that
uses BindTo=dev-%i.device to
This patch adds the WatchdogRestartSec and WatchdogRebootSec
properties to services. Systemd will restart the service / reboot the
system if the watchdog timeout has not been updated for the configured
amount of time.
This functionality is only enabled if the watchdog timeout is set at
least once.
This patch adds WatchdogTimestamp[Monotonic] to the systemd service
D-Bus API. The timestamp is updated to the current time when the
service calls 'sd_nofity(WATCHDOG=1\n)'.
Using a timestamp instead of an 'alive' flag has two advantages:
1. No timeout is needed to define when a service is no
This patch introduces a small watchdog daemon that supervises systemd
and handles /dev/watchdog. This is mostly a prove of concept for now.
---
Makefile.am| 22 -
src/99-systemd.rules.in|2 +
src/watchdogd.c| 178
This patch adds WatchdogRebootTimestamp[Monotonic] to the systemd
manager API. It contains the earliest point in time when systemd might
reboot the system because the timer for WatchdogRebootUSec for a
service expired.
If we assume the system takes Xus to shut down then
WatchdogRebootTimestamp +
