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