On Sat, 23 Aug 2014, Nico Kadel-Garcia wrote:
On Sat, Aug 23, 2014 at 4:49 AM, Vladimir Mosgalin
<[email protected]> wrote:
Hi Denice!
On 2014.08.22 at 16:31:42 -0700, Denice wrote next:
This summer our Co-op student, Samuel Lai, wrote a script for us that
implements the systemctl command as a script. It can be used to manage
many aspects of the init system at SL5 and SL6.
We have made it available at:
http://grid.triumf.ca/share/
in case you are interested, and you haven't already implemented
your own script.
That was certainly a funny idea! Neat.
Personally I think that using Fedora is better experience in trying
systemd (after all, it has many other aspects like managing system
settings with timedatectl/localectl/hostnamectl/etc instead of files in
/etc/sysconfig, which might not work as before in systemd-based system),
but this is an interesting approach.
I checked this rpm, no surprises or malicious code (really, I suggest
everyone to check scripts of rpm package and all the files before
installing it when downloading some totally random rpm off the net -
fortunately, it's pretty simple in this case).
I do like the idea, for testing systemd based tools in Scientific
Linux 6 based environments. I'd particularly like to see it in EPEL,
where all RHEL compatible flavors of Linux can benefit.
Getting it to be ubiquitous for SL 6 and SL 5 could make my life
noticeably easier maintaining backports of things like Subversion, and
Samba, for SL 6.
If there is anyone on the list who maintains things in EPEL already,
and would like to add this script to their list of managed packages,
then we would be happy to pass it over to them. Presumably it will
not need many revisions after the first few fixes. Otherwise it takes
a bit of time to get yourself added into the list of maintainers.
Our student is going back to university, and needs to turn his
attention to other activities.
cheers,
Denice
As for the actual script, it has problem parsing xinetd-based services.
Check out partial output of chkconfig --list:
wpa_supplicant 0:выкл 1:выкл 2:выкл 3:выкл 4:выкл 5:выкл 6:выкл
xinetd 0:выкл 1:выкл 2:выкл 3:вкл 4:вкл 5:вкл 6:выкл
xl2tpd 0:выкл 1:выкл 2:выкл 3:выкл 4:выкл 5:выкл 6:выкл
ypbind 0:выкл 1:выкл 2:выкл 3:выкл 4:выкл 5:выкл 6:выкл
службы на основе xinetd:
chargen-dgram: выкл
chargen-stream: выкл
daytime-dgram: выкл
What we get with systemctl list-unit-files?
wpa_supplicant.service 3:выкл
xinetd.service 3:вкл
xl2tpd.service 3:выкл
ypbind.service 3:выкл
службы.service
chargen-dgram.service
chargen-stream.service
daytime-dgram.service
Obviously it won't be able to manage xinetd services with "service
start/stop" so it might be beter to skip them from output, and
службы.service is a parsing error for trying to parse header of "xinetd
based services". It assumed for some reason that everyone is using
english locale. Duh. It should've set LANG=C if it wants to parse based
on english string!
--
Vladimir
--
deatrich @ triumf.ca, Science/ATLAS PH: +1 604-222-7665
<*> This moment's fortune cookie:
Barker's Proof:
Proofreading is more effective after publication.
