Alexander Skwar <[EMAIL PROTECTED]> writes:
> The problem is, that in older installations NETWORKING was set to "true",
> and because "true" != "yes", xinetd would stop. Also this:
so why -o true ?
> [root@teich /etc/init.d]# grep NETWORKING *
> dhcpd:[ ${NETWORKING} = "no" ] && exit 0
> identd:if [ ${NETWORKING} = "no" ]
> inet:if [ ${NETWORKING} = "no" ]
> jabber:[ ${NETWORKING} = "no" ] && exit 0
> ldap:[ ${NETWORKING} = "no" ] && exit 0
> lpd:[ ${NETWORKING} = "no" ] && exit 0
> netfs:[ ${NETWORKING} = "no" ] && exit 0
> network:[ ${NETWORKING} = "no" ] && exit 0
> portmap:if [ ${NETWORKING} = "no" ]
> postfix:[ ${NETWORKING} = "no" ] && exit 0
> squid:[ ${NETWORKING} = "no" ] && exit 0
> vmware: vmware_networking=`db_load_answer "$vmware_db" 'NETWORKING'`
> xinetd:[ -z "$NETWORKING" -o "$NETWORKING" = "no" ] && exit 0
> xntpd:[ ${NETWORKING} = "no" ] && exit 0
>
> My version also takes care of the case you mentioned, because I let xinetd
> exit when $NETWORKING isn't set at all.
>
> Hmm, you might want to change the changelog to this, to clarify it:
> - Changed init script to exit when $NETWORKING isn't set or is set to no;
> IOW: the initscript continues when NETWORKING is set to anything, but not
> to no. Before init script would exit if NETWORKING != yes
>
> Alexander Skwar
--
MandrakeSoft Inc http://www.chmouel.org
Paris, France --Chmouel
