[opensuse] Re: new to systemd - rcnetwork status - equivalent needed
Patrick Shanahan wrote:
* cagsm
[01-25-12 09:59]: new to systemd - rcnetwork status - equivalent needed
wondering how i can list those nice details to all my network interface cards and connections, like with rcnetwork status, and also rcnetwork start dsl0 and so on. systemd seems like a pita. any good pointers? tia.
I have found that most of the rc..... utilities still function and a plus, they provide the corresponding systemd function, ie:
10:01 Crash: ~ # rcnetwork status redirecting to systemctl network.service - LSB: Configure the localfs depending network interfaces Loaded: loaded (/etc/init.d/network) Active: active (running) since Sat, 21 Jan 2012 11:38:13 -0500; 3 days ago CGroup: name=systemd:/system/network.service ├ 2394 /sbin/dhclient6 -6 -cf -/var/lib/dhcp6/dhclient6.eth0.conf -/-lf -/-/var/lib/dhcp6/dhclient6.eth0.lease -/-/-pf /var... └ 6718 sbin/dhcpcd netconfig L -E HHH c etc/sysconfig/network/scripts/dhcpcd-hook /-----/-t 0 h Crash eth0 10:02 Crash: ~ 3
note that line wrap will distort the information display. There are 8 lines. The systemd corresponding cmd comes after CGroup:... systemctl status network.service
But that's not what cagsm wanted. He wanted the whole status info that rcnetwork status used to output. The problem here is, IMNSHO, a severe design mismatch on a high level between the old init.d and the new systemd concept. init.d looked at services as something very general. In fact, anything that shall be started at boot time, ended at shutdown time, or manually in-between, and that might output some status info, is a service for init.d. Anything that might be of interest for a human can be output by the services' status command. For systemd, a service is an initialization of something, or a group of running processes with a master process. A status info is just the information which processes that are, as shown in the example output above, and nothing more. openSUSE systemd proponents, in particular Cristian Rodriguez, have repeatedly called any further wish as unreasonable. I don't know if that view is shared at systemd upstream development, though postings that I've seen indicate that this might be the case (see below for links). If you want, you can read a discussion thread at the opensuse-factory list archive with the subject "Re: Human readable, what is that? (was [12.1] massive data loss in /var/tmp/)", mid to end December. It quickly went downhill into a flame war between systemd oponents and proponents, as happens so often. But inbetween there were postings that presented several use cases for an "ExecStatus" configuration possibility that executes an arbitrary command to get the status. Particularly, LXC container status and AppArmor status were mentioned. These were summarily discarded by Cristian and others. (Cristian was the most vocally, that's why I remember him specifically.) Actually, since their answers did not address the actual use case parts that were cited as problematic, I even prepared a summary post that tried to re-formulate them and addressed specifically Cristian if he could react on these issues technically and not in a polemic way. Sadly, Cristian didn't answer. I don't know if he didn't see it, was fed up by the flame war, or chose to ignore it for other reasons. I don't know the state of the "ExecStatus" proposal upstream, the first three Google page results didn't get me that information. In August, Lennart was against it: http://permalink.gmane.org/gmane.comp.sysutils.systemd.devel/3171. In November, a bugzilla ticket mentions it might be needed, but Kay was also very sceptical: https://bugzilla.redhat.com/show_bug.cgi?id=754127 -- that ticket is not yet closed. In the source, there is a notion of ExecStatus in src/execute.[ch], but I couldn't recognize at first glance if that is about the existing restricted status notion of systemd, or about the eventual introduction of a full ExecStatus configuration possibility. Hope this summary of events that I have read about in the context of service status helps. Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod@acm.org Roedermark, Germany -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Joachim Schrod
Patrick Shanahan wrote:
I have found that most of the rc..... utilities still function and a plus, they provide the corresponding systemd function, ie:
...
But that's not what cagsm wanted. He wanted the whole status info that rcnetwork status used to output.
I must have mis-understood his request. Unfortunately, the informationa returned by "rcnetwork status" was not complete or completely valid. Ie, from a servier I maintain still running 11.2 on sysinitv: wahoo:~ > rcnetwork status eth0 has unknown interface type. Please file a bug report. lo has unknown interface type. Please file a bug report. wlan0 has unknown interface type. Please file a bug report. Checking optional network interfaces: eth0 device: ADMtek NC100 Network Everywhere Fast Ethernet 10/100 (rev 11) No configuration found for eth0 eth0 unused wlan0 is not available wlan0 dead Checking mandatory network interfaces: lo No configuration found for lo lo dead Checking service network . . . . . . . . . . . dead Service "netowrk" is up and active on eth0 which is configured in yast and is the connection to wahoo server. I guess a better and more informative answer to "network status" would have been "ifconfig" which provides much of the above although in much different format.
If you want, you can read a discussion thread at the opensuse-factory list archive with the subject "Re: Human readable, what is that? (was [12.1] massive data loss in /var/tmp/)", mid to end December. It quickly went downhill into a flame war
I did read this thread and agree that *most* of it was posturing and uninformative or completely off-topic, an unfortunate problem with lists that have no moderator. Thanks for your informative digest. I see much good and much lacking in systemd, but it appears to be the *future*. I guess it is time to be issuing multiple and plentiful bug reports :^). tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
I get no such crap output from rcnetwork status on 11.4 or lower. Maybe it's a 12.1 thing. nj12:~ # rcnetwork status Checking optional network interfaces: br0 br0 IP address: 10.0.0.212/24 br0 is up running br1 br1 IP address: 98.109.178.98/24 br1 is up running eth0 device: Intel Corporation 82576 Gigabit Network Conne eth0 is up running eth1 device: Intel Corporation 82576 Gigabit Network Conne eth1 is up running vethWIMyqp No configuration found for vethWIMyqp unused vethXJtuqp No configuration found for vethXJtuqp unused vetho7zVqp No configuration found for vetho7zVqp unused Checking mandatory network interfaces: lo lo IP address: 127.0.0.1/8 secondary lo IP address: 127.0.0.2/8 lo is up running Checking service network . . . . . . . . . . . . . running nj12:~ # The veth's are the host sides of lxc container vm's "no configuration" isn't an error. Granted I never use "rcnetwork status" myself either. But that's only because that one is a special case. I happen to know "ip addr" and "ifconfig" because they are essentially universal to every box every distro every version, even other os's in the case of ifconfig. I don't know off hand the similar commands for every other service. Nor do I want my people to all have to know them. It's valuable to have a consistent interface, ie "rc<service> status" that never the less outputs different, service-specific, human-meaningful output depending on the service. Systemd goes out of it's way not to know anything service specific, treating them all the same and only knowing a basic item that's the same for all, ie is the daemon running or not, is a socket listening or not. Not things like, what are the statuses of the individual cups queues, or my own example the statuses of individual vm's as well as the overall status of the vm-running-facility. (poor example, rccups doesn't output queue statuses, but it could, saving admins from having to know lpstat -t or whatever the cups equivalent is, and the lxc example is more important because there is actually no server daemon, just the possibility of one or more vm's running. You have to check them all and if at least one is running, then the "service" is up, if no vm's are running, then the "service" is down. Other vm systems will have similar but different quirks in how they are managed.) To me it comes down to, init allows you to be messy, and systemd hates that mess so much it disallows the ability to be flexible and do any jobs other than a few rigidly defined types, resulting in admittedly tidier service management, for those services that systemd even acknowledges as such, which admittedly covers most common ones. Anything else you want to do, oh well, tough. Unix used to be about flexibility. -- bkw On 1/25/2012 3:11 PM, Patrick Shanahan wrote:
* Joachim Schrod
[01-25-12 14:37]: Patrick Shanahan wrote:
I have found that most of the rc..... utilities still function and a plus, they provide the corresponding systemd function, ie:
...
But that's not what cagsm wanted. He wanted the whole status info that rcnetwork status used to output.
I must have mis-understood his request.
Unfortunately, the informationa returned by "rcnetwork status" was not complete or completely valid. Ie, from a servier I maintain still running 11.2 on sysinitv:
wahoo:~> rcnetwork status eth0 has unknown interface type. Please file a bug report. lo has unknown interface type. Please file a bug report. wlan0 has unknown interface type. Please file a bug report. Checking optional network interfaces: eth0 device: ADMtek NC100 Network Everywhere Fast Ethernet 10/100 (rev 11) No configuration found for eth0 eth0 unused wlan0 is not available wlan0 dead Checking mandatory network interfaces: lo No configuration found for lo lo dead Checking service network . . . . . . . . . . . dead
Service "netowrk" is up and active on eth0 which is configured in yast and is the connection to wahoo server.
I guess a better and more informative answer to "network status" would have been "ifconfig" which provides much of the above although in much different format.
If you want, you can read a discussion thread at the opensuse-factory list archive with the subject "Re: Human readable, what is that? (was [12.1] massive data loss in /var/tmp/)", mid to end December. It quickly went downhill into a flame war
I did read this thread and agree that *most* of it was posturing and uninformative or completely off-topic, an unfortunate problem with lists that have no moderator.
Thanks for your informative digest. I see much good and much lacking in systemd, but it appears to be the *future*. I guess it is time to be issuing multiple and plentiful bug reports :^).
tks,
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Brian K. White
I get no such crap output from rcnetwork status on 11.4 or lower. Maybe it's a 12.1 thing.
the data I provided was output from rcnetwork status on an x86_64 11.2 openSUSE headless server, *not* from 12.1. 19:04 wahoo:~ > rcnetwork status eth0 has unknown interface type. Please file a bug report. lo has unknown interface type. Please file a bug report. wlan0 has unknown interface type. Please file a bug report. Checking optional network interfaces: eth0 device: ADMtek NC100 Network Everywhere Fast Ethernet 10/100 (rev 11) No configuration found for eth0 eth0 unused 19:04 wahoo:~ > ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:04:5A:55:39:C8 inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::204:5aff:fe55:39c8/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:15325113 errors:0 dropped:0 overruns:0 frame:0 TX packets:24776950 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:4250665841 (4053.7 Mb) TX bytes:29404705756 (28042.5 Mb) Interrupt:17 Base address:0xac00 -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
Brian K. White
-
Joachim Schrod
-
Patrick Shanahan