Hi,
isn't that a bug in e2fsck anyway? There is accept_time_fudge which
defaults to true and should take care of this situation. Even when it
wouldn't default to true, my e2fsck.conf already had its alias
buggy_init_scripts set to 1. Nevertheless, I'm briefly seeing an fsck
running now on every bo
Package: resolvconf
Version: 1.75
Followup-For: Bug #749405
On Sun, Jun 01, 2014 at 10:59:00AM +0100, Edward Allcutt wrote:
>
> Dear Maintainer,
>
> I generally concur with Andre, with one exception.
>
> I believe the WantedBy line should reference networking.service as that
> will be pulled in
Hi,
I was affected by the same bug and found that resolvconf.service, while
loaded, was actually never run by systemd (jessie). Now I know nothing
about systemd and the bizarre maze of targets and services it comprises,
but it appeared to me that network.target might not be the ideal target
to use
3 matches
Mail list logo
