-nodes --format=tmpfiles
On Wed, Apr 5, 2023 at 11:13 AM Richard Hector <mailto:rich...@walnut.gen.nz>> wrote:
Hi all,
I want to create a device (/dev/fuse) in an LXC container. The kernel
bit works; I can mknod manually, but I'd rather use a systemd unit, and
make it a d
Hi all,
I want to create a device (/dev/fuse) in an LXC container. The kernel
bit works; I can mknod manually, but I'd rather use a systemd unit, and
make it a dependency of mounting filesystems from /etc/fstab.
It looks like .device units are supposed to be created automatically if
there's
Hi all,
Quoting from another thread:
On 5/09/20 4:36 am, Lennart Poettering wrote:
> Unit instances can be activated on-the-fly without further prepartion
> or regsitration of the instance string or so. it's sufficient if the
> template unit exists.
Is that preventable?
I have some instance
On 27/08/20 1:43 am, Lennart Poettering wrote:
> On Mi, 26.08.20 11:26, Richard Hector (rich...@walnut.gen.nz) wrote:
>
>> Hi all,
>>
>> I've got the common warning:
>>
>> /lib/systemd/system/fail2ban.service:12: PIDFile= references path below
>> leg
On 26/08/20 9:07 pm, Reindl Harald wrote:
>
>
> Am 26.08.20 um 01:26 schrieb Richard Hector:
>> Hi all,
>>
>> I've got the common warning:
>>
>> /lib/systemd/system/fail2ban.service:12: PIDFile= references path below
>> legacy directory /var/
2020 at 4:27 PM Richard Hector <mailto:rich...@walnut.gen.nz>> wrote:
>
> Hi all,
>
> I've got the common warning:
>
> /lib/systemd/system/fail2ban.service:12: PIDFile= references path below
> legacy directory /var/run/, updating /var/run/fail2ban/fa
Hi all,
I've got the common warning:
/lib/systemd/system/fail2ban.service:12: PIDFile= references path below
legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid →
/run/fail2ban/fail2ban.pid; please update the unit file accordingly.
I made the change in the relevant override.conf
On 29/07/20 4:13 am, Ian Pilcher wrote:
> On 7/28/20 11:07 AM, Mantas Mikulėnas wrote:
>> I'd create a single raidcheck.service that runs daily and calls a
>> script that itself determines which device to check, e.g.
>> /dev/md$[dayofyear % 16].
>
> That is the approach that I'm taking, although
