On 07/07/2014 04:53 PM, Reindl Harald wrote:
And thus it is not in RHEL 6. If an admin has not been working with Fedora, then there is no experience with it. Plus it was easy to ignore systemctl in Fedora for a while, though by F18 it was hard to say the least.
Yes the wrapper is there, but at least on Fedora, I notice that related items like chkconfig no longer worked as well, and I really needed to buckle down and learn systemctl.
Which was a great hint to figure out what this systemctl was all about.
Robert Moskowitz wrote:
Wasn't there an upstart somewhere?
I think I'll write an alias for chkconfig to systemctl. *bleah* As far as I'm concerned, it was a solution to something that wasn't a problem, just like this urge to make config files xml.
mark
On 07/07/2014 05:04 PM, m.roth@5-cent.us wrote:
Oh, I don't mean that it is not there. Rather it doesn't interact the way it use to. For example on F20:
chkconfig
Note: This output shows SysV services only and does not include native systemd services. SysV configuration data might be overridden by native systemd configuration.
If you want to list systemd services use 'systemctl list-unit-files'. To see services enabled on particular target use 'systemctl list-dependencies [target]'.
netconsole 0:off 1:off 2:off 3:off 4:off 5:off 6:off network 0:off 1:off 2:off 3:off 4:off 5:off 6:off
====================================
Basically telling you to get with the program.
On 07/07/2014 05:04 PM, m.roth@5-cent.us wrote:
Wasn't there an upstart somewhere?
:-)
Why, of course, as in: [lowen@dhcp-pool107 ~]$ rpm -qa|grep ^upstart upstart-0.6.5-13.el6_5.3.x86_64 [lowen@dhcp-pool107 ~]$
This box is CentOS 6. Upstart was around for a few Fedora releases up through F14; I don't recall when it was introduced, but wikipedia tells me it was F9.
It was a problem for some, even if not for you or for me.
-
Lamar Owen -
m.roth＠5-cent.us -
Robert Moskowitz