You are not logged in.
Pages: 1
Why the most of programs at rc.d don't have the "status" action? For example, on CentOS, the httpd (Apache Server) has the below actions:
httpd {start|stop|restart|condrestart|reload|status|fullstatus|graceful|help|configtest}
while httpd of Arch has only actions:
httpd {start|stop|restart|reload}
Furthermore, the scripts of CentOS is very well commented and the most of scripts of Arch have shallow and fewer comments.
Last edited by alessandro_ufms (2008-07-29 20:58:37)
Offline
You are welcome to submit patches against any or all of Arch's init scripts, with accompanying reasons for their inclusion. If you decide to do this, they will be evaluated by the relevant maintainers, who will decide whether they wish to follow your suggestions.
Offline
The function exists. It's just a matter of using it in the scripts. I think there's stuff on the bug tracker about it too.
[git] | [AURpkgs] | [arch-games]
Offline
That's just the standard vanilla way that rc.d files have been done on Arch for the longest time. Every file has start, stop, and restart. Anything else has been viewed as excess.
You want the status? `ps -a | grep httpd`
You want more? `ps aux | grep httpd`
You want to test the config? Well, you got me there, I don't know that off the top of my head.
These things can be automated, if you want I could get you a rc.d script that does all this, someone could submit it to the devs, and it MIGHT replace the original one if they decide the extra functionality is worth including.
Offline
Pages: 1