Control: reopen -1
I'm not sure what to do with this really.
Yesterday I upgraded my wheezy system and come to this very issue there.
Because I had systemd installed from wheezy-backports, and now this bug
reappeared in a backported version, ofcourse initscripts in wheezy is
not patched.
At least
On 14/06/14 06:32, Michael Biebl wrote:
Am 08.06.2014 00:37, schrieb Jason Alavaliant:
I've just tested the latest initscripts package (2.88dsf-53.1)
Jason, could you please test again with 2.88dsf-53.2?
53.1 had an embarrasing formatting error.
I've retested with 2.88dsf-53.2 and confirmed t
Am 08.06.2014 00:37, schrieb Jason Alavaliant:
> I've just tested the latest initscripts package (2.88dsf-53.1)
Jason, could you please test again with 2.88dsf-53.2?
53.1 had an embarrasing formatting error.
--
Why is it that all of the instruments seeking intelligent life in the
universe are p
Hi Michael,
> How do you configure your network? Do you use ifupdown vi
> /etc/network/interfaces and if so, is the interface marked as auto or
> allow-hotplug.
this is quite new installation which uses NetworkManager. So my
/etc/network/interfaces configures just lo:
$ cat /etc/network/interfa
Am 08.06.2014 00:37, schrieb Jason Alavaliant:
> I've just tested the latest initscripts package (2.88dsf-53.1)
>
> Unfortunately the lines in adds to /etc/network/if-up.d/mountnfs ;
>
> --
> # Skip the mountnfs hook when being triggered by the networking SysV init
> # script and
I've just tested the latest initscripts package (2.88dsf-53.1)
Unfortunately the lines in adds to /etc/network/if-up.d/mountnfs ;
--
# Skip the mountnfs hook when being triggered by the networking SysV init
# script and instead use the systemd built-in mechanisms to mount remote
Are you sure you are using the new script? What kind of error do you still
encounter?
On 7. Juni 2014 23:08:06 MESZ, david wrote:
>Unfortunately the new version of initscripts (2.88dsf-53.1)
>has a modified mountnfs script which reintroduces this bug.
>
>The patch in an earlier post had fixed
Unfortunately the new version of initscripts (2.88dsf-53.1)
has a modified mountnfs script which reintroduces this bug.
The patch in an earlier post had fixed it. I don't know
enough to be able to patch the new script so i hope
somebody here will be able to come up with something.
Am 06.06.2014 14:01, schrieb Petr Vorel:
> Package: systemd
> Followup-For: Bug #746358
>
> Dear Maintainer,
>
> I have NFS mounted by default in my /etc/fstab and I didn't suffer to this
> bug after
> upgrade.
How do you configure your network? Do you use ifupdo
I ran into this problem and the patch in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746358#20 fixed it.
Commenting out my NFS mounts worked also, but I couldn't figure out how to
get to an editor short of using a rescue CD. (i.e. even in a "recovery
mode" boot, I'd
I want to clarify one thing: 204-8 works fine, described behavior
applies only to 204-10 and 208-1.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
I think I hit the the same bug, but I don't have any NFS mounts or
bridge interfaces. It started happening afer upgrade to 204-10 (I
skipped 204-9) and is also present in 208-1. 204-8 works fine and that
is the version I'm currently running.
My system sometimes starts normally, sometimes it hangs
A few extra cents worth may help here.
1. I can confirm that the patch given earlier fixes the boot time bug.
2. For a long time I have had a delay, say 30 sec, during startup. Now
during that delay the message "Starting a job for LSB: Raising Network
Interfaces" appears. (That's not the exact
Hi Daniel,
Am 04.05.2014 11:20, schrieb Daniel Leidert:
> I also have some NFS entries in my /etc/fstab and I manually
> patched /etc/network/if-up.d/mountnfs as suggested after I upgraded the
> system. However: the system still hangs on startup for 1-2 minutes
> saying:
>
> [ OK ] Started LSB: N
Hi,
I also have some NFS entries in my /etc/fstab and I manually
patched /etc/network/if-up.d/mountnfs as suggested after I upgraded the
system. However: the system still hangs on startup for 1-2 minutes
saying:
[ OK ] Started LSB: NFS support files common to client and server
[ **] (X of Y) A
severity 746358 serious
thanks
Am 30.04.2014 11:58, schrieb Aurelien Jarno:
> Given that systemd is now the default, if every persons with an NFS entry
> in fstab will get their systems broken, it might be a good idea to increase
> the severity of this bug.
It's not yet the default (via the sysvi
Am 30.04.2014 11:58, schrieb Aurelien Jarno:
> On Tue, Apr 29, 2014 at 03:10:02PM +0200, Michael Biebl wrote:
>> Am 29.04.2014 13:10, schrieb Jason Alavaliant:
>>> On 2014-04-29 22:36, Michael Biebl wrote:
Am 29.04.2014 11:31, schrieb Jason Alavaliant:
>>
Do you have an NFS / remote fs co
On 30/04/14 01:10, Michael Biebl wrote:
Am 29.04.2014 13:10, schrieb Jason Alavaliant:
On 2014-04-29 22:36, Michael Biebl wrote:
Am 29.04.2014 11:31, schrieb Jason Alavaliant:
Do you have an NFS / remote fs configuration in your /etc/fstab?
Yes I've got a nfs4 mounted home directory
server.loc
On Tue, Apr 29, 2014 at 03:10:02PM +0200, Michael Biebl wrote:
> Am 29.04.2014 13:10, schrieb Jason Alavaliant:
> > On 2014-04-29 22:36, Michael Biebl wrote:
> >> Am 29.04.2014 11:31, schrieb Jason Alavaliant:
>
> >> Do you have an NFS / remote fs configuration in your /etc/fstab?
> >
> > Yes I'v
Am 29.04.2014 13:10, schrieb Jason Alavaliant:
> On 2014-04-29 22:36, Michael Biebl wrote:
>> Am 29.04.2014 11:31, schrieb Jason Alavaliant:
>> Do you have an NFS / remote fs configuration in your /etc/fstab?
>
> Yes I've got a nfs4 mounted home directory
> server.local:/ /home nfs4
On 2014-04-29 22:36, Michael Biebl wrote:
Am 29.04.2014 11:31, schrieb Jason Alavaliant:
Package: systemd
Version: 204-10
Severity: important
Dear Maintainer,
I just updated my system which installed systemd-sysv
after I rebooted I found that the system was now hanging
on bootup (even in rescu
Am 29.04.2014 11:31, schrieb Jason Alavaliant:
> Package: systemd
> Version: 204-10
> Severity: important
>
> Dear Maintainer,
>
> I just updated my system which installed systemd-sysv
> after I rebooted I found that the system was now hanging
> on bootup (even in rescue mode) with the stopping p
22 matches
Mail list logo
