You are not logged in.
Pages: 1
Hi,
Is it normal to still have rc.d in /etc?
Should I remove these/do something with them?
me@host /etc/rc.d $ ls
avahi-daemon crond ip6tables krb5-kdc ntpd preload
avahi-dnsconfd ftpd iptables krb5-kpropd ntpdate rsyncd
bluetooth functions.d krb5-kadmind mdadm ppp sshd
me@host /etc $ ls -a | grep rc
mail.rc
rc.d
rc_keymaps
rc_maps.cfg
I see init still exists, but it seems to actually be sustemd
me@host /etc :( $ init --help
systemd [OPTIONS...]
Starts up and maintains the system or user services.
Note, systemd handles these it seems:
me@host /etc/systemd/system/multi-user.target.wants $ ls -a
. lm_sensors.service ntpd.service sshd.service
.. net-auto-wireless.service preload.service ufw.service
cronie.service netctl@ButterNet.service remote-fs.target
EDIT: not using code tags make unicorns cry
Last edited by MilenKid (2013-05-10 13:12:44)
Offline
Yes, it is normal if the maintainers haven't yet removed them from the packages. Until then they cause no harm, if you remove them they will be recreated when the package is updated
Offline
The /etc/rc.d/* files you have left simply have not been removed from the packages yet. I guess mostly because the packages didn't get upstream updates since initscripts was deprecated and it's not worth to make a new package release just to remove some dead files. This is happening slowly, but at some point they will be completely gone.
If you want to get rid of them, use the NoExtract option from pacman.conf.
and please use [ code ] tags in the future.
Offline
The /etc/rc.d/* files you have left simply have not been removed from the packages yet. I guess mostly because the packages didn't get upstream updates since initscripts was deprecated and it's not worth to make a new package release just to remove some dead files. This is happening slowly, but at some point they will be completely gone..
I fail to see this ever happening & if this does/is happening then this is more proof that systemd is forcing itself on others, Linux has always been about choice as there are many init alternatives it is simply down to the package developers whether an init script is included in a given package or not & whether the script is present or not within packages is down to the distro's package maintainers to remove.
So initscripts will never be depreciated unless we see the day when all other init systems are removed & systemd is the only one left.
Sorry if this appeared as flamey, that was not my intention 'tis only my opinion which I will always voice
ROG Strix (GD30CI) - Intel Core i5-7400 CPU - 32Gb 2400Mhz - GTX1070 8GB - AwesomeWM (occasionally XFCE, i3)
If everything in life was easy, we would learn nothing!
Linux User: 401820 Steam-HearThis.at-Last FM-Reddit
Offline
I fail to see this ever happening
Really? We will be doing a rebuild to get rid of all the old rc.d files soon...
Offline
I fail to see this ever happening
uhm, it already is happening, a lot of rc.d scripts have already been removed.
Linux has always been about choice as there are many init alternatives it is simply down to the package developers whether an init script is included in a given package or not & whether the script is present or not within packages is down to the distro's package maintainers to remove.
I think you are misunderstanding something here. The rc.d scripts are not provided by the developers of the application, they are provided by the Arch Linux developers (who decided not to waste their time on them anymore, that's why they are being removed).
Offline
t0m5k1, Arch initscripts IS deprecated, and has been for months now. The Arch specific scripts that were added to packages are being removed. Period.
Nobody is claiming that SysV or BSD style init is deprecated, but once and for all, ARCH INITSCRIPTS IS DEPRECATED. Saying anything else is an unhealthy level of denial you might want to seek help for.
Offline
Got it and thanks for the tag's tip.
Question is, for example I have both cronie.service and crond in rc.d, which is the one used? (how can I find out myself?)
ps doesn't seem to help finding out who started it:
host ~ # ps -aux | grep cron
root 419 0.0 0.0 13240 1352 ? Ss 09:02 0:00 /usr/sbin/crond -n
root 16514 0.0 0.0 10900 1120 pts/0 S+ 16:14 0:00 grep --color=auto cron
Last edited by MilenKid (2013-05-10 13:15:09)
Offline
I see most have misread what I typed, my perspective was not purely ARCHcentric
ROG Strix (GD30CI) - Intel Core i5-7400 CPU - 32Gb 2400Mhz - GTX1070 8GB - AwesomeWM (occasionally XFCE, i3)
If everything in life was easy, we would learn nothing!
Linux User: 401820 Steam-HearThis.at-Last FM-Reddit
Offline
I see most have misread what I typed, my perspective was not purely ARCHcentric
The rc.d files in question are "ARCHcentric", so you're saying your post was just off topic, then?
Offline
Question is, for example I have both cronie.service and crond in rc.d, which is the one used? (how can I find out myself?)
ps doesn't seem to help finding out who started it:
host ~ # ps -aux | grep cron root 419 0.0 0.0 13240 1352 ? Ss 09:02 0:00 /usr/sbin/crond -n root 16514 0.0 0.0 10900 1120 pts/0 S+ 16:14 0:00 grep --color=auto cron
You are running systemd, no? So, of course it is cronie running. You need to do some reading here: https://wiki.archlinux.org/index.php/Systemd
I see most have misread what I typed, my perspective was not purely ARCHcentric
As Scimmia said, scripts under rc.d are arch specific, written by arch maintainers, not upstream.
I think some developers (upstream) provide sysvinit service files, but not initscript files. But I don't know what arch maintainers do with *those* files.
Last edited by x33a (2013-05-10 13:37:44)
Offline
You are running systemd, no? So, of course it is cronie running. You need to do some reading here: https://wiki.archlinux.org/index.php/Systemd
I did. I don't know why everyone is assuming that I do not read the documentation. I thought it's obvious from my question.
But as long as rc files should not exist (they have no point), I thought maybe start-up is done in the old way.
Thanks.
Offline
Pages: 1