Date: Sun, 04 Jan 2004 14:32:58 -0500 From: Scott W <wegster@mindcore.net> To: Micke P <mickep3@yahoo.com> Cc: freebsd-questions@freebsd.org Subject: Re: starting daemons at server start Message-ID: <3FF86A6A.3010109@mindcore.net> In-Reply-To: <20040104192156.86503.qmail@web14525.mail.yahoo.com> References: <20040104192156.86503.qmail@web14525.mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Micke P wrote: >Right! Ok, it's definitely not inetd that I need. I'm >thinking primarily of starting apache and a dynamic ip >updater automatically at startup. > >Micke > > >--- fbsd_user <fbsd_user@a1poweruser.com> wrote: > > >>Maybe you just don't understand what you are seeing. >>Inetd is the >>Super server. Every thing you uncomment in the >>inetd.conf file is an >>server of it own right. But instead of an daemon >>running for telnet >>or FTP all the time. Inetd runs and listens on the >>ports where those >>services would be listings and when inetd sees an >>request on the >>specified port it automatically launches the server >>for that >>service. With inetd running , ps ax only shows inetd >>running, but >>start an telnet session to your box and you will see >>that inetd has >>spawned an telnet server session. When your telnet >>users leaves the >>session, the telnet server terminates. Inetd is used >>to conserve >>resources. >> >> If you installed apache from ports, there should already be a apache-dist.sh script in /usr/local/etc/rc.d . Copy it to apache.sh, chmod 600 (or at least make it executable), and apache should start at system reboot. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3FF86A6A.3010109>