On Fri, Mar 22, 2002 at 15:23:45 +1030, Tom Cook wrote:
>
> The current behaviour is far more sensible to a non-expert user than
> the opposite behaviour, where he installs (say) apache, then bombards
> the list with messages with the subject 'broken apache - doesn't
> start' so that he can be tol
> for i in `find . -type f -name S90telnetd` ; do
> mv $i `echo $i | sed s/S90telnetd/K90telnetd` ;
> done
>
> There is probably a much easier way of doing it than that, but it
> works, and this is my opinion, after all.
update-inetd --disable telnet
just did it today, found it in the *upda
On 0, Vincent Lefevre <[EMAIL PROTECTED]> wrote:
> Most (all?) packages providing a daemon or other service will start
> it when installed, without asking the user first. Is there a reason?
> I often want to have such services ready for use (with documentation
> and configuration files), but not s
Most (all?) packages providing a daemon or other service will start
it when installed, without asking the user first. Is there a reason?
I often want to have such services ready for use (with documentation
and configuration files), but not started immediately, i.e. not
running by default.
One exam
4 matches
Mail list logo
