On Sat, 5 Sep 2020, Richard Hector wrote:
> 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 un
On 05/09/2020 13:18, Kevin P. Fleming wrote:
> It's a general issue with templated unit files; I've had this happen
> as well, and could not figure out why the service had failed to start.
> It was because I had mistyped the instance name. As best I can tell
> systemd doesn't have any mechanism to
It's a general issue with templated unit files; I've had this happen
as well, and could not figure out why the service had failed to start.
It was because I had mistyped the instance name. As best I can tell
systemd doesn't have any mechanism to restrict the instance names
which can be used for a s
I've run into similar issues and resorted to adding battery-backed
RTCs to my RPis in order to ensure that the kernel's clock would be
set to something 'reasonable' very early in the boot process (although
it's still not ideal since the RTC drivers are loaded as modules so
the kernel's code for doi
On Sa, 05.09.20 09:49, Andrei Borzenkov (arvidj...@gmail.com) wrote:
> 05.09.2020 01:05, Lennart Poettering пишет:
> >
> > I explained this already. DNS server data today is much less config
> > than state, acquired dynamically via DHCP, hence most distros don#t
> > configure it in /etc so much an
