Hello all, I *know* this is a touchy subject, so please don't turn this into yet-another-why-I-hate-systemd shouting-match. (God knows we had far too many of those lately...) I'm in the process of upgrading a number of F14 machines to F15. (Which makes me a prime candidate for a "I survived Fedora 15" T-shirt *). In a number of these machines, the network service refuses to work preventing a clean OS boot (I'm being thrown into Emergency console; most likely udev persistent names is playing havoc with my network cards order). So, my question is rather (?) simple: Back in old days /etc/init.d/network used to throw (semi-)informative error messages; 'systemctl start network.service' is silent and 'systemctl status network.service' returns a meaningless error code. How can I force systemctl start to dump the complete service output to the console? (Preferably without adding some boot parameters and/or configuration file editing) Thanks, - Gilboa * Couldn't resist the urge, sorry :) -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
