Somewhere along the line my particular problem with NFS mounts failing to work
at boot with systemd has been fixed on all of my systems.
I've kept up to date with upgrading Debian packages on all of my systems, and
one of these seems to have addressed my problems.
But I couldn't say which one it
> Am 31.10.2014 um 01:30 schrieb Jim Barber:
> > My network config on the host is very simple:
> >
> >$ cat /etc/network/interfaces
> ># This file describes the network interfaces available on your system
> ># and how to activate them. For more information, see interfaces(5).
> >
> >
Am 31.10.2014 um 01:30 schrieb Jim Barber:
> Package: systemd
> Version: 215-5+b1
>
> Hi.
>
> I have a similar problem, and I think it belongs in this bug report.
> On boot, NFS file systems used to work fine.
> It was after upgrading from initscripts version 2.88dsf-53.4 to 2.88dsf-57
> that al
Package: systemd
Version: 215-5+b1
Hi.
I have a similar problem, and I think it belongs in this bug report.
On boot, NFS file systems used to work fine.
It was after upgrading from initscripts version 2.88dsf-53.4 to 2.88dsf-57 that
all my NFS mounts no longer mount on boot.
I was going to repor
Control: reopen -1
Control: found -1 215-5+b1
On Sun, 14 Sep 2014 17:20:47 +0200 Michael Biebl wrote:
> I'm going to close this bug for now. If you still encounter any issues
> and you have additional information, please let us know, so we can
> reopen the bug report.
I'm seeing this issue and i
Am 05.07.2014 17:12, schrieb Michael Biebl:
> Am 22.02.2014 00:16, schrieb John Paul Adrian Glaubitz:
>> On 02/22/2014 12:10 AM, Michael Biebl wrote:
>>> Just tried again (with two VMs):
>>> The NFS server being a wheezy system, the client system is an up-to-date
>>> SID system. Worked like a charm
Am 22.02.2014 00:16, schrieb John Paul Adrian Glaubitz:
> On 02/22/2014 12:10 AM, Michael Biebl wrote:
>> Just tried again (with two VMs):
>> The NFS server being a wheezy system, the client system is an up-to-date
>> SID system. Worked like a charm.
>
> Ok, it seems to be a local configuration is
severity 739721 normal
thanks
On 02/22/2014 12:10 AM, Michael Biebl wrote:
> Just tried again (with two VMs):
> The NFS server being a wheezy system, the client system is an up-to-date
> SID system. Worked like a charm.
Ok, it seems to be a local configuration issue then. I will try to pin
point
Am 21.02.2014 23:40, schrieb John Paul Adrian Glaubitz:
> On Fri, Feb 21, 2014 at 11:30:24PM +0100, Michael Biebl wrote:
>>> # The loop back interface
>>> auto lo
>>> iface lo inet loopback
>>>
>>> auto eth0
>>
>> Does changing to "allow-hotplug eth0" make a difference?
>
> Unfortunately, no. The
On Fri, Feb 21, 2014 at 11:30:24PM +0100, Michael Biebl wrote:
> > # The loop back interface
> > auto lo
> > iface lo inet loopback
> >
> > auto eth0
>
> Does changing to "allow-hotplug eth0" make a difference?
Unfortunately, no. The behavior is still the same.
> > iface eth0 inet static
> > ad
Am 21.02.2014 23:22, schrieb John Paul Adrian Glaubitz:
> Hi Michael!
>
> Thanks for your quick reply!
>
> On Fri, Feb 21, 2014 at 11:04:46PM +0100, Michael Biebl wrote:
>> Please include more details about your network setup and the nfs
>> configuration.
>> The nfs shares should be mounted via t
Hi Michael!
Thanks for your quick reply!
On Fri, Feb 21, 2014 at 11:04:46PM +0100, Michael Biebl wrote:
> Please include more details about your network setup and the nfs
> configuration.
> The nfs shares should be mounted via the nfs ifupdown hooks which worked
> successfully last time I tested
Am 21.02.2014 22:48, schrieb John Paul Adrian Glaubitz:
> Package: systemd
> Version: 204-6
> Severity: important
>
> Hi!
>
> I am writing this bug report to raise the awareness about this issue among
> the Debian systemd maintainers and to make sure it gets resolved before
> we release Jessie wh
13 matches
Mail list logo
