Oliver Lehmann wrote:
> Hi Doug,
>
> Doug Barton wrote:
>
>> Also, the assignment of pidfile should really come after the defaults are
>> set.
>>
>> If you do all that and it still doesn't work, send a diff of your two rc.d
>> scripts to the list.
>
> PROVIDE is in both cases "utility" (probably a generic unchanged default)
> - I've changed it to utility2 for bacula-fd2 with no changes. Here the diff:
That's arguably a bug. It should be something more descriptive. The
standard is that the name of the script file, the $name variable and
the PROVIDE line should all match.
> r...@nudel rc.d> diff -u bacula-fd*
> --- bacula-fd 2009-02-15 23:25:03.000000000 +0100
> +++ bacula-fd2 2009-03-02 20:22:40.000000000 +0100
> @@ -16,16 +16,16 @@
>
> . /etc/rc.subr
>
> -name="bacula_fd"
> +name="bacula_fd2"
> rcvar=${name}_enable
> command=/usr/local/sbin/bacula-fd
>
> load_rc_config $name
>
> -pidfile="${bacula_fd_pidfile}"
> +pidfile="${bacula_fd2_pidfile}"
You missed the bit where I said that this should come after the
assignment of the defaults below.
> -: ${bacula_fd_enable="NO"}
> -: ${bacula_fd_flags=" -u root -g wheel -v -c /usr/local/etc/bacula-fd.conf"}
> -: ${bacula_fd_pidfile="/var/run/bacula-fd.9102.pid"}
> +: ${bacula_fd2_enable="NO"}
> +: ${bacula_fd2_flags=" -u root -g wheel -v -c
> /usr/local/etc/bacula-fd2.conf"}
> +: ${bacula_fd2_pidfile="/var/run/bacula-fd.9104.pid"}
>
> run_rc_command "$1"
> Exit 1
> r...@nudel rc.d> grep bacula_fd /etc/rc.conf
> bacula_fd_enable="YES"
> bacula_fd2_enable="YES"
> bacula_fd2_flags=" -u root -g wheel -v -c /usr/local/etc/bacula-fd2.conf"
> bacula_fd2_pidfile="/var/run/bacula-fd.9104.pid"
Have you confirmed that the two pid files exist, and that they contain
the right information?
Doug
--
This .signature sanitized for your protection
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
