Thanks for the helpful info.. It's clear now; I should start off with ssh
client.
Regards,
Vidol
----- Original Message -----
From: Nalin Dahyabhai <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, August 01, 2001 11:46 PM
Subject: Re: Telnet as a standalone?
> On Wed, Aug 01, 2001 at 06:59:09AM +0700, loeung vidol wrote:
> > Thanks for the suggestion. I'll look for those client programs.
> > Well, I still would like to know how we can convert an xinetd-dependent
> > service to a standalone one.
>
> Generally, the server needs to be written to support standalone
> operation in addition to being invoked by xinetd or inetd. For
> example, both Samba and the Apache web server support both.
>
> I don't believe you can do this with the standard telnetd included in
> the distribution -- a peek at the man page (man in.telnetd) shows that
> the standalone mode is only meant for use when debugging the telnet
> server.
>
> Apache and Samba are run in a standalone mode in order to avoid the
> potentially large startup overhead incurred when inetd starts up a new
> copy of the server, which is much higher than what you'd get when a
> standalone listener forks off a copy of itself to handle an incoming
> connection.
>
> For the telnet server, I wouldn't worry about it, since most of the work
> done when someone logs in using telnet is actually being done by login,
> and you can't get around that by switching to a standalone server.
>
> Cheers,
>
> Nalin
>
>
>
> _______________________________________________
> Seawolf-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/seawolf-list
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
