Hi Bill,

Thanks for the info.

cheers
anand

Bill Marcum wrote:
quote:

> On Tue, 24 Jun 2003 17:34:37 +0530, Anand Rao
>   <anand.rao@oracle.com> wrote: 
> Inetd starts a server when that service is requested.  Netstat or some
> similar tool should show inetd listening on port 21.
> 
> man ftpd
> man inetd
>
> --
> It is often the case that the man who can't tell a lie thinks he is the be
st
> judge of one.
>                 -- Mark Twain, "Pudd'nhead Wilson's Calendar"

[ Post a follow-up to this message ]

Hi Chris,

Thanks for the info. Yeah, i thought it was the same like telnetd ...the pro
cess
appears only when there is a connection... but wanted to make sure i was not
just guessing. Thanks again for the explanations too.

cheers
anand

Chris Mattern wrote:
quote:

> Anand Rao wrote: 
>
> When somebody connects to your box to a service maintained by inetd,
> they actually connect to inetd.  Inetd then starts the necessary server
> and hooks the incoming connection up to it.  You see in.telnetds because
> there are people currently connected to your box using telnet.  You
> don't see in.ftpds because nobody is currently connected using ftp.
> 
>
> No.  Inetd starts.  Inetd then starts in.ftpds when somebody connects
> to the port you configured in inetd.conf for in.ftpd.
> 
>
> If you've modified /etc/services, all you need to do is kill -HUP inetd
> to make it reread its conf file; when it does so, it will look up port
> "ftp" in /etc/services and start listening on the new port for incoming
> ftp connections.  If you want my advice, however, I would not redefine
> ftp in /etc/services.  Modify inetd.conf to use the new port by number
> instead of the port name ftp.  The first argument in each line in inetd.co
nf
> is the port inetd listens on to start a service (the service started is
> the sixth and seventh arguments).  So just change the line that starts
> ftp to whatever port number you want to listen on, and change /etc/service
s
> back the way it was.
>
>                  chris Mattern

[ Post a follow-up to this message ]

Hi Chris,

Thanks for the info. Yeah, i thought it was the same like telnetd ...the pro
cess
appears only when there is a connection... but wanted to make sure i was not
just guessing. Thanks again for the explanations too.

cheers
anand

Chris Mattern wrote:
quote:

> Anand Rao wrote: 
>
> When somebody connects to your box to a service maintained by inetd,
> they actually connect to inetd.  Inetd then starts the necessary server
> and hooks the incoming connection up to it.  You see in.telnetds because
> there are people currently connected to your box using telnet.  You
> don't see in.ftpds because nobody is currently connected using ftp.
> 
>
> No.  Inetd starts.  Inetd then starts in.ftpds when somebody connects
> to the port you configured in inetd.conf for in.ftpd.
> 
>
> If you've modified /etc/services, all you need to do is kill -HUP inetd
> to make it reread its conf file; when it does so, it will look up port
> "ftp" in /etc/services and start listening on the new port for incoming
> ftp connections.  If you want my advice, however, I would not redefine
> ftp in /etc/services.  Modify inetd.conf to use the new port by number
> instead of the port name ftp.  The first argument in each line in inetd.co
nf
> is the port inetd listens on to start a service (the service started is
> the sixth and seventh arguments).  So just change the line that starts
> ftp to whatever port number you want to listen on, and change /etc/service
s
> back the way it was.
>
>                  chris Mattern

[ Post a follow-up to this message ]

Hi Juhana,

Thanks for the info. Yeah, i thought it was the same like telnetd ...the pro
cess
appears only when there is a connection... but wanted to make sure i was not
 just
guessing. Thanks for the pointers too.

cheers
anand


Juhana Siren wrote:
quote:

> Anand Rao <anand.rao@oracle.com> writes:
> 
>
> Yes. inetd starts it when a connection is made to the port specified
> in the services file.
> 
>
> I'd say modifying the services file should be enough.
> 
>
> You probably know the usual channels for further info: the man pages
> for ftpd, inetd, and inetd.conf; http://docs.sun.com/ is also a good
> source for Solaris-specific answers.
>
> --
> ****** Juhana Siren ***** Juhana.Siren@oulu.fi ***** OH8HTH (2 m, 70 cm) *
*****
> It is a lesser evil to embarrass oneself with a silly question than by bre
aking
> something. --me--

[ Post a follow-up to this message ]

Hi Juhana,

Thanks for the info. Yeah, i thought it was the same like telnetd ...the pro
cess
appears only when there is a connection... but wanted to make sure i was not
 just
guessing. Thanks for the pointers too.

cheers
anand


Juhana Siren wrote:
quote:

> Anand Rao <anand.rao@oracle.com> writes:
> 
>
> Yes. inetd starts it when a connection is made to the port specified
> in the services file.
> 
>
> I'd say modifying the services file should be enough.
> 
>
> You probably know the usual channels for further info: the man pages
> for ftpd, inetd, and inetd.conf; http://docs.sun.com/ is also a good
> source for Solaris-specific answers.
>
> --
> ****** Juhana Siren ***** Juhana.Siren@oulu.fi ***** OH8HTH (2 m, 70 cm) *
*****
> It is a lesser evil to embarrass oneself with a silly question than by bre
aking
> something. --me--

[ Post a follow-up to this message ]

Hi Bill,

Thanks for the info.

cheers
anand

Bill Marcum wrote:
quote:

> On Tue, 24 Jun 2003 17:34:37 +0530, Anand Rao
>   <anand.rao@oracle.com> wrote: 
> Inetd starts a server when that service is requested.  Netstat or some
> similar tool should show inetd listening on port 21.
> 
> man ftpd
> man inetd
>
> --
> It is often the case that the man who can't tell a lie thinks he is the be
st
> judge of one.
>                 -- Mark Twain, "Pudd'nhead Wilson's Calendar"

[ Post a follow-up to this message ]

Hi Chris,

Thanks for the info. Yeah, i thought it was the same like telnetd ...the pro
cess
appears only when there is a connection... but wanted to make sure i was not
just guessing. Thanks again for the explanations too.

cheers
anand

Chris Mattern wrote:
quote:

> Anand Rao wrote: 
>
> When somebody connects to your box to a service maintained by inetd,
> they actually connect to inetd.  Inetd then starts the necessary server
> and hooks the incoming connection up to it.  You see in.telnetds because
> there are people currently connected to your box using telnet.  You
> don't see in.ftpds because nobody is currently connected using ftp.
> 
>
> No.  Inetd starts.  Inetd then starts in.ftpds when somebody connects
> to the port you configured in inetd.conf for in.ftpd.
> 
>
> If you've modified /etc/services, all you need to do is kill -HUP inetd
> to make it reread its conf file; when it does so, it will look up port
> "ftp" in /etc/services and start listening on the new port for incoming
> ftp connections.  If you want my advice, however, I would not redefine
> ftp in /etc/services.  Modify inetd.conf to use the new port by number
> instead of the port name ftp.  The first argument in each line in inetd.co
nf
> is the port inetd listens on to start a service (the service started is
> the sixth and seventh arguments).  So just change the line that starts
> ftp to whatever port number you want to listen on, and change /etc/service
s
> back the way it was.
>
>                  chris Mattern

[ Post a follow-up to this message ]

Hi Juhana,

Thanks for the info. Yeah, i thought it was the same like telnetd ...the pro
cess
appears only when there is a connection... but wanted to make sure i was not
 just
guessing. Thanks for the pointers too.

cheers
anand


Juhana Siren wrote:
quote:

> Anand Rao <anand.rao@oracle.com> writes:
> 
>
> Yes. inetd starts it when a connection is made to the port specified
> in the services file.
> 
>
> I'd say modifying the services file should be enough.
> 
>
> You probably know the usual channels for further info: the man pages
> for ftpd, inetd, and inetd.conf; http://docs.sun.com/ is also a good
> source for Solaris-specific answers.
>
> --
> ****** Juhana Siren ***** Juhana.Siren@oulu.fi ***** OH8HTH (2 m, 70 cm) *
*****
> It is a lesser evil to embarrass oneself with a silly question than by bre
aking
> something. --me--

[ Post a follow-up to this message ]

Hi Bill,

Thanks for the info.

cheers
anand

Bill Marcum wrote:
quote:

> On Tue, 24 Jun 2003 17:34:37 +0530, Anand Rao
>   <anand.rao@oracle.com> wrote: 
> Inetd starts a server when that service is requested.  Netstat or some
> similar tool should show inetd listening on port 21.
> 
> man ftpd
> man inetd
>
> --
> It is often the case that the man who can't tell a lie thinks he is the be
st
> judge of one.
>                 -- Mark Twain, "Pudd'nhead Wilson's Calendar"

[ Post a follow-up to this message ]

Hi Chris,

Thanks for the info. Yeah, i thought it was the same like telnetd ...the pro
cess
appears only when there is a connection... but wanted to make sure i was not
just guessing. Thanks again for the explanations too.

cheers
anand

Chris Mattern wrote:
quote:

> Anand Rao wrote: 
>
> When somebody connects to your box to a service maintained by inetd,
> they actually connect to inetd.  Inetd then starts the necessary server
> and hooks the incoming connection up to it.  You see in.telnetds because
> there are people currently connected to your box using telnet.  You
> don't see in.ftpds because nobody is currently connected using ftp.
> 
>
> No.  Inetd starts.  Inetd then starts in.ftpds when somebody connects
> to the port you configured in inetd.conf for in.ftpd.
> 
>
> If you've modified /etc/services, all you need to do is kill -HUP inetd
> to make it reread its conf file; when it does so, it will look up port
> "ftp" in /etc/services and start listening on the new port for incoming
> ftp connections.  If you want my advice, however, I would not redefine
> ftp in /etc/services.  Modify inetd.conf to use the new port by number
> instead of the port name ftp.  The first argument in each line in inetd.co
nf
> is the port inetd listens on to start a service (the service started is
> the sixth and seventh arguments).  So just change the line that starts
> ftp to whatever port number you want to listen on, and change /etc/service
s
> back the way it was.
>
>                  chris Mattern

[ Post a follow-up to this message ]