On Fri, 2005-09-30 at 09:49 +0200, Eduard Bloch wrote:
> > 
> > You mean change
> >     XPSERVERLIST="`/etc/init.d/xprint get_xpserverlist`"
> > to
> >     XPSERVERLIST="`/etc/init.d/xprint get_xpserverlist || true`"
> > ?
> 
> Of course. Or foo=`bar` || true, or foo=`bar || :` or whatever.
> 
> > Easy enough to do of course, but since it would be preferable to
> > actually run the script, wouldn't it be better to try
> > 
> >     XPSERVERLIST="`/bin/bash /etc/init.d/xprint get_xpserverlist`"
> > 
> > instead?
> 
> More robust, but not much more. If some error happens in the script the
> Xsession is broken again (see other bug report).
> 

OK.  I'll probably use XPSERVERLIST="`/etc/init.d/xprint
get_xpserverlist || true`" then I think, on the grounds that if the
local admin has made /etc/init.d/xprint non-executable, then they must
really not want it executed. So I'll let the Xsession.d script honour
that policy (not that I understand such a policy myself. Why would
anyone want to disable execution of init scripts? Or is the idea here to
disable some daemons, while still having their packages installed?)

Drew


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to