Re: starting pkgsrc services on 1.4
On Thu, Dec 29, 2005 at 11:54:58AM -0800, Cheese Lottery wrote: It seems that in order to use pkgsrc's rc.d scripts, I do not set name_enable as with the base system scripts, I just set name. Am I right? Yes Also, what is the recommended way to ensure that the pkgsrc rc.d scripts are run on start up? Right now, I have set PKG_RCD_SCRIPTS=YES in my mk.conf, which copies pkgsrc's rc.d scripts to /etc/rc.d. This is one of the options. I normally link them manually, since I want to know whatI want to run. P.S. A nitpick about pkgsrc/mail/postfix. The included rc.d script attempts to copy files from /etc to /var/spool/postfix/etc. This fails because /var/spool/postfix/etc is not created when the package is installed. I know, I complained more than once about it :-) I'm going to fix it myself... Joerg
Re: starting pkgsrc services on 1.4
:I'm trying out 1.4 RC1 right now. : :It seems that in order to use pkgsrc's rc.d scripts, I do not set :name_enable as with the base system scripts, I just set name. Am I :right? Yup. It looks like the pkgsrc RC scripts use the base name rather then name_enable. :Also, what is the recommended way to ensure that the pkgsrc rc.d :scripts are run on start up? Right now, I have set PKG_RCD_SCRIPTS=YES :in my mk.conf, which copies pkgsrc's rc.d scripts to /etc/rc.d. :Otherwise, they are not run. Is there a better way? (I think FreeBSD :has recently made changes to the way rc.d scripts from ports are :handled. Is this change applicable to DragonFly?) There is a chicken-and-egg problem here in that /usr itself is not mounted at the time the system RC is run. I think what we want to do is have an RC script in /etc/rc.d which chains to the other RC directories. i.e. that runs its own rcorder that includes the additional rc.d directories, figures out what hasn't been run yet, and runs it. We aren't going to be able to do this for the release, but it would make a great post-release project. -Matt Matthew Dillon [EMAIL PROTECTED]
Re: starting pkgsrc services on 1.4
On Thu, Dec 29, 2005 at 11:54:58AM -0800, Cheese Lottery wrote: P.S. A nitpick about pkgsrc/mail/postfix. The included rc.d script attempts to copy files from /etc to /var/spool/postfix/etc. This fails because /var/spool/postfix/etc is not created when the package is installed. Please send-pr it or notify the maintainer ([EMAIL PROTECTED]) about this. http://www.netbsd.org/cgi-bin/sendpr.cgi?gndb=netbsd (Category: pkg) Geert
Re: starting pkgsrc services on 1.4
No wait, I take it back. There is a chaining script already in our /etc/rc.d called /etc/rc.d/localdaemons. It isn't picking up the scripts because they do not have a .sh suffix. Sigh, that bites us in the ass again. It was a bad idea to have non-.sh and .sh RC scripts. I am going to fix this in HEAD... that is, allow script directories listed in local_startup (/usr/pkg/etc/rc.d, /usr/local/etc/rc.d, etc) to not have a .sh option, but I just don't know whether it is a good idea to put in -RELEASE. It could generate unintended side effects. -Matt Matthew Dillon [EMAIL PROTECTED]
Re: starting pkgsrc services on 1.4
On Thu, Dec 29, 2005 at 12:34:38PM -0800, Matthew Dillon wrote: There is a chicken-and-egg problem here in that /usr itself is not mounted at the time the system RC is run. Anything in /usr should depend on e.g. NETWORKING or similiar hooks, which ensure that it is started late enough to not have to worry about it. Splitting off into other directories adds a lot of head aches, since you couldn't order anything from pkgrsc before base rc scripts, e.g. as needed for postfix. Joerg
Re: starting pkgsrc services on 1.4
On 12/29/05, Matthew Dillon [EMAIL PROTECTED] wrote: No wait, I take it back. There is a chaining script already in our /etc/rc.d called /etc/rc.d/localdaemons. It isn't picking up the scripts because they do not have a .sh suffix. Sigh, that bites us in the ass again. It was a bad idea to have non-.sh and .sh RC scripts. I am going to fix this in HEAD... that is, allow script directories listed in local_startup (/usr/pkg/etc/rc.d, /usr/local/etc/rc.d, etc) to not have a .sh option, but I just don't know whether it is a good idea to put in -RELEASE. It could generate unintended side effects. I looked it up, here is what FreeBSD has done: http://article.gmane.org/gmane.os.freebsd.stable/33936 (description) http://tinyurl.com/b5kn8 (code) So they run rcorder, run the scripts until finishing mountcritremote, re-run rcorder against both base and local rc.d scripts, skip the scripts that have already run, and run the rest. (I think?)
