Am 27.02.2011 22:36, schrieb Michael Biebl:
My sugggestion would be something like this:
in net.agent:
if [ -d /sys/fs/cgoup/systemd ] ; then
systemctl start ifup@$INTERFACE.service
else
exec ifup --allow=hotplug $INTERFACE
fi
and provide a instanced ifup@.serivce file, which
On 28.02.2011 17:29, Michael Biebl wrote:
Hi Michael,
My sugggestion would be something like this:
in net.agent:
if [ -d /sys/fs/cgoup/systemd ] ; then
systemctl start ifup@$INTERFACE.service
else
exec ifup --allow=hotplug $INTERFACE
fi
and provide a instanced ifup@.serivce file,
On 18.02.2011 08:24, Tollef Fog Heen wrote:
| No. This is a very basic Squeeze installation in a KVM VM.
Ok.
| However, I do see weird things, namely duplicate mounts.
Looks like you don't have /etc/mtab pointing to /proc/mounts?
Correct. Fixed that, does not fix my non-starting network
Am 27.02.2011 22:24, schrieb Bernhard Schmidt:
On 18.02.2011 08:24, Tollef Fog Heen wrote:
| However, I do see weird things, namely duplicate mounts.
Looks like you don't have /etc/mtab pointing to /proc/mounts?
Correct. Fixed that, does not fix my non-starting network though.
Upgrading
Am 27.02.2011 22:36, schrieb Michael Biebl:
My sugggestion would be something like this:
in net.agent:
if [ -d /sys/fs/cgoup/systemd ] ; then
systemctl start ifup@$INTERFACE.service
else
exec ifup --allow=hotplug $INTERFACE
fi
For completeness sake, Tollef was suggestion
On 16.02.2011 21:57, Michael Biebl wrote:
Am 16.02.2011 21:50, schrieb Bernhard Schmidt:
I'm not sure where to look further. I tried redirecting the stderr and
stdout of the actual ifup invocation to a file in /dev, but I always end
up with an empty file. Not sure why.
Do you have separate
]] Bernhard Schmidt
| No. This is a very basic Squeeze installation in a KVM VM.
Ok.
| However, I do see weird things, namely duplicate mounts.
Looks like you don't have /etc/mtab pointing to /proc/mounts?
| Could this be related somehow? A mount command directly before the
| ifup in
]] Michael Biebl
| So you might start adding some debugging output there to find out what is
going
| wrong on your system.
Hi,
have you had a chance to take a look at debugging this?
Regards,
--
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are
--
To
On 16.02.2011 21:34, Tollef Fog Heen wrote:
Hi,
| So you might start adding some debugging output there to find out what is
going
| wrong on your system.
have you had a chance to take a look at debugging this?
Sorry, I completely forgot.
Please find hotplug.log attached. I added two
Am 16.02.2011 21:50, schrieb Bernhard Schmidt:
I'm not sure where to look further. I tried redirecting the stderr and
stdout of the actual ifup invocation to a file in /dev, but I always end
up with an empty file. Not sure why.
Do you have separate partitions for /var, /tmp or /usr ?
On 25.01.2011 21:58, Tollef Fog Heen wrote:
Hi,
| After upgrading from systemd 11-1 to 16-1 my eth0 is not started
| automatically anymore. Replacing
|
| allow-hotplug eth0 (which is default after d-i)
|
| with
|
| auto eth0
|
| in /etc/network/interfaces it works as expected.
Can you see if
]] Bernhard Schmidt
| On 25.01.2011 21:58, Tollef Fog Heen wrote:
|
| Can you see if /etc/network/run is a symlink to /lib/init/rw or /dev/shm
| or a regular directory, please?
|
| It is a regular directory. This is a plain squeeze installation from
| about two months ago in a VM, only
On 31.01.2011 14:04, Tollef Fog Heen wrote:
Hi,
Yeah, this is a known bug in ifupdown that it doesn't create that
directory properly as a symlink. Just make it a symlink to
/lib/init/rw/network or /dev/shm/network and it should work better.
(This is documented in README.Debian)
Done,
On 31.01.2011 14:09, Bernhard Schmidt wrote:
On 31.01.2011 14:04, Tollef Fog Heen wrote:
Hi,
Yeah, this is a known bug in ifupdown that it doesn't create that
directory properly as a symlink. Just make it a symlink to
/lib/init/rw/network or /dev/shm/network and it should work better.
]] Bernhard Schmidt
| After upgrading from systemd 11-1 to 16-1 my eth0 is not started
| automatically anymore. Replacing
|
| allow-hotplug eth0 (which is default after d-i)
|
| with
|
| auto eth0
|
| in /etc/network/interfaces it works as expected.
Can you see if /etc/network/run is a
Package: systemd
Version: 16-1
Severity: normal
After upgrading from systemd 11-1 to 16-1 my eth0 is not started
automatically anymore. Replacing
allow-hotplug eth0 (which is default after d-i)
with
auto eth0
in /etc/network/interfaces it works as expected.
-- System Information:
Debian
16 matches
Mail list logo
