Le 07/11/2011 17:41, Ville Skyttä a écrit :
On 11/07/2011 05:12 PM, Igor Murzov wrote:
I pushed new variant of the fix to the "service" branch. Can you look into it?
I didn't look into the code that closely, but it works as expected in
all test cases I threw at it, cool.
The branch seems to be lagging behind some commits from master, so be
careful not to lose them when merging it.
On Sun, 06 Nov 2011 17:44:38 +0200
Ville Skyttä<[email protected]> wrote:
I've eyeballed the xinetd.d part earlier too and I have a feeling that
it shouldn't be used in this context anyway and that part should
probably be just removed. xinetd services are not to my knowledge
managed by the same tools or used the same way as sysv init ones anyway.
I have nothing to say about this. Haven't used it at all.
It seems it was Guillaume who submitted the patch that added it, see
commit 13ac864. Guillaume, comments?
Ouch, back in 2004 :)
chkconfig and system commands have minimal support for xinetd services:
[root@beria bash-completion]# service rsync status
rsync is a xinetd service and it is disabled
to activate it do the following command:
chkconfig rsync on
[root@beria bash-completion]# chkconfig --list rsync
Note: This output shows SysV services only and does not include native
systemd services. SysV configuration data might be overriden by
native
systemd configuration.
rsync arrêt
So, it's still valid to include them in services list.
--
BOFH excuse #290:
The CPU has shifted, and become decentralized.
_______________________________________________
Bash-completion-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/bash-completion-devel
