737641 – systemd: rcnetwork start implies stop

Bug 737641 - systemd: rcnetwork start implies stop

Summary: systemd: rcnetwork start implies stop

Status:	VERIFIED DUPLICATE of bug 727771

Alias:	None

Product:	openSUSE 12.2
Classification:	openSUSE
Component:	Basesystem (show other bugs)
Version:	Factory
Hardware:	PowerPC-64 Linux

Priority:	P5 - None Severity: Normal (vote)
Target Milestone:	---
Assignee:	Marius Tomaschewski
QA Contact:	E-mail List

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2011-12-19 13:27 UTC by Jan Engelhardt
Modified:	2012-01-06 04:26 UTC (History)
CC List:	2 users (show)

See Also:
Found By:	Beta-Customer
Services Priority:
Business Priority:
Blocker:	---
Marketing QA Status:	---
IT Deployment:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Jan Engelhardt 2011-12-19 13:27:38 UTC

Something is not right here..

silver:~ # rcnetwork start / systemctl start network.service
redirecting to systemctl
Hint: you may set mandatory devices in /etc/sysconfig/network/config
Setting up network interfaces:
    eth0      device: Broadcom Corporation NetXtreme BCM5704 Gigabi
    eth0      IP address: 134.76.43.9/26   
              IP address: 2001:638:600:3351::2/64                    waiting
    eth1      device: Broadcom Corporation NetXtreme BCM5704 Gigabi
              No configuration found for eth1                        unused
Setting up service network  .  .  .  .  .  .  .  .  .  .             done
silver:~ # Shutting down network interfaces:
    eth0      device: Broadcom Corporation NetXtreme BCM5704 Gigabi  done
    eth1      device: Broadcom Corporation NetXtreme BCM5704 Gigabi
              No configuration found for eth1 
              Nevertheless the interface will be shut down.          done
Shutting down service network  .  .  .  .  .  .  .  .  .             done

silver:~ # rpm -q systemd
systemd-37-7.1.ppc
sysconfig-0.75.4-5.3.ppc

Why is it shutting down the service after it was started?

Comment 1 Marius Tomaschewski 2011-12-21 10:39:44 UTC

Last change were basically the addition of

# X-Systemd-RemainAfterExit: true

to /etc/init.d/network and /etc/init.d/network-remotefs.

When your scripts don't have add it -- when they have it revert either
setting it to "false" or removing them.

Does it help?

Comment 2 Marius Tomaschewski 2011-12-22 09:10:01 UTC

BTW: See also bug 736059 and bug 732930 and references.

Comment 3 Marius Tomaschewski 2012-01-04 18:47:57 UTC

I think this is a duplicate of bug 727771, resolving as such.

*** This bug has been marked as a duplicate of bug 727771 ***

Comment 4 Jan Engelhardt 2012-01-06 04:26:21 UTC

The systemd update alone seems to have fixed it. (RemainAfterExit=yes according to sysctl show network.service now.)