David Härdeman writes:
> I've experienced the same problem with k5start in Jessie. The problem is
> that with systemd and systemd-networkd, the machine boots so quickly
> that the network isn't up when my service unit (using k5start) is
> executed...meaning the daemon never gets started (unless I
Package: kstart
Version: 4.1-3
Followup-For: Bug #705063
Dear Maintainer,
I've experienced the same problem with k5start in Jessie. The problem is
that with systemd and systemd-networkd, the machine boots so quickly
that the network isn't up when my service unit (using k5start) is
executed...mean
On Tue, Apr 09, 2013 at 10:01:50AM -0700, Russ Allbery wrote:
> Dominic Hargreaves writes:
>
> > Whilst troubleshooting an issue with startup of a daemon invoked via
> > k5start and supervise, we noticed that k5start appears to exit, rather
> > than retrying, if it is unable to resolve DNS (in th
Dominic Hargreaves writes:
> Whilst troubleshooting an issue with startup of a daemon invoked via
> k5start and supervise, we noticed that k5start appears to exit, rather
> than retrying, if it is unable to resolve DNS (in this case, the local
> caching resolver was not started, owing to system s
Package: kstart
Version: 4.1-2
Severity: normal
Whilst troubleshooting an issue with startup of a daemon invoked via
k5start and supervise, we noticed that k5start appears to exit, rather
than retrying, if it is unable to resolve DNS (in this case, the local
caching resolver was not started, owing
5 matches
Mail list logo
