Date: Fri, 21 Dec 2001 15:30:35 +0200 From: Maxim Sobolev <sobomax@FreeBSD.org> To: Ernst de Haan <ernsth@nl.euro.net> Cc: Ernst de Haan <znerd@FreeBSD.org>, ports@FreeBSD.org Subject: Re: Starting a service after installation? Message-ID: <3C23397B.E9A1A197@FreeBSD.org> References: <200112211144.fBLBif252175@zaphod.euronet.nl> <3C23295E.37E26CAD@FreeBSD.org> <200112211311.fBLDBCt66721@zaphod.euronet.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Ernst de Haan wrote:
>
> On Friday 21 December 2001 13:21, Maxim Sobolev wrote:
> > Ernst de Haan wrote:
> > > Hey all,
> > >
> > > How should services like an application server (i.e. www/orion or
> > > www/jakarta-tomcat) be started at boot time?
> > >
> > > I was thinking we could something like this, for example for www/orion:
> > > 1) During installation, install a script in ${PREFIX}/etc/rc.d. In this
> > > case orion.sh. Make it +x so it can be executed. The www/orion port (and
> > > a lot of other ports) already do this.
> > > 2) Make the script so that it checks if it should be started by reading
> > > /etc/rc.conf and /etc/defaults/rc.conf. For example, for www/orion, it
> > > could check for "start_orion". If this variable is not found, then the
> > > service is perhaps not started (or should it) ? If the variable *is*
> > > found then the service will only be started if the value matches
> > > [Yy][Ee][Ss]
> > >
> > > I'm also assuming that starting a service right after installation is a
> > > Bad Thing^TM. What about a 'make run' ? ;`/
> >
> > Usually FreeBSD ports use different strategy. The service installs
> > startup script into /usr/local/etc/rc.d, in the case when the service
>
> Yes, this is what I described in (1). But I would like to *extend* the
> current approach. What if I installed a port like Orion, but I *don't* want
> it to be started at system startup? In my suggestion you would add:
>
> start_orion="NO"
>
> to your /etc/rc.conf file.
>
> > startup script into /usr/local/etc/rc.d, in the case when the service
> > is expected to be "on" right after installation this script is named
>
> "is expected to be "on"" ? What if the user installing the script would like
> the service to be off by default? Perhaps we should introduce a variable for
> this so one can do something like:
>
> make START_AT_BOOT=NO install
>
> whoch would in turn add something like
>
> start_<servicename>="NO"
>
> to /etc/rc.conf...
>
> Just braindumping here ;)
IMO /etc/rc.conf is only for the services in the base system,
configuration for optional packages should go elsewhere.
-Maxim
>
> Ernst
>
> > fooservice.sh, but when the service is to be disable by default - the
> > script is named fooservice.sh.sample. The script should take either
> > "start" or "stop" argument - the former automatically supplied by
> > /etc/rc.* during a machine startup, while the latter - during a
> > shutdown. You can find plenty of examples in the ports tree usable as
> > a template for such script.
> >
> > And I don't really think that you need something like `make run'
> > because it's not much easier than direct call to appropriate script.
> > Instead you could tweak the port to emit during post-install a message
> > saying that the user should run `${PREFIX}/etc/rc.d/fooservice start'
> > if he want to start the service right now.
> >
> > -Maxim
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3C23397B.E9A1A197>