(In reply to comment #36)
> (In reply to comment #35)
> > If I remove the "auto ..." line from /etc/network/interfaces, the problem
> > appears again.
> >
> > I can see the "Configuring network interfaces" and "Waiting for network
> > interface to come up" messages, all OK, but the "Synchronizing clock..." failed
> > (sometimes).
> >
>
> Could you add the following lines to the top (below any comments) of
> /etc/init.d/hotplug-net, /etc/hotplug/net.agent and /etc/hotplug/net.ifup
>
> ----8<--------8<--------8<--------8<----
> exec 2>>/tmp/network.log
> date 1>&2
> echo "$0" "$@" 1>&2
> set -x
> ---->8-------->8-------->8-------->8----
>
> Then do a reboot, if it fails attach /tmp/network.log
>
> Thanks
Mmmm... Rather strange... I added the above lines in the three files you tell
me, I removed the "auto ..." line from e/n/i, I booted several (seven or eight)
times, and I'm unable to reproduce the bug :/
It could be casualness, or maybe the problem is now solved (but I don't know
why... perhaps because of an update...)
Can you give me one more day to study this in detail, and to try to reproduce
the bug?
(In reply to comment #36) interfaces, the problem d/hotplug- net, /etc/hotplug/ net.agent and /etc/hotplug/ net.ifup ------- 8<----- ---8<-- ------8< ---- ------- >8----- --->8-- ------> 8----
> (In reply to comment #35)
> > If I remove the "auto ..." line from /etc/network/
> > appears again.
> >
> > I can see the "Configuring network interfaces" and "Waiting for network
> > interface to come up" messages, all OK, but the "Synchronizing clock..." failed
> > (sometimes).
> >
>
> Could you add the following lines to the top (below any comments) of
> /etc/init.
>
> ----8<-
> exec 2>>/tmp/network.log
> date 1>&2
> echo "$0" "$@" 1>&2
> set -x
> ---->8-
>
> Then do a reboot, if it fails attach /tmp/network.log
>
> Thanks
Mmmm... Rather strange... I added the above lines in the three files you tell
me, I removed the "auto ..." line from e/n/i, I booted several (seven or eight)
times, and I'm unable to reproduce the bug :/
It could be casualness, or maybe the problem is now solved (but I don't know
why... perhaps because of an update...)
Can you give me one more day to study this in detail, and to try to reproduce
the bug?
Thanks a lot.