Date: Thu, 28 Apr 2022 19:40:12 +0200 (CEST) From: Sysadmin Lists <sysadmin.lists@mailfence.com> To: freebsd-hackers@freebsd.org Cc: Eugene Grosbein <eugen@grosbein.net>, Axel Rau <Axel.Rau@chaos1.de> Subject: Re: rc script to let a service wait for db available Message-ID: <187283243.91660.1651167612801@ichabod.co-bxl> In-Reply-To: <fba9b121-6a2e-daf6-a1ea-64227ad8266d@grosbein.net> References: <f6201772-d124-a08f-3623-25f1a6190faf@Chaos1.DE> <c17abf27-0997-5627-b9c8-98a76d8946a3@grosbein.net> <dd303c84-9f54-78a5-16e2-81d32f2033d3@Chaos1.DE> <fba9b121-6a2e-daf6-a1ea-64227ad8266d@grosbein.net>
next in thread | previous in thread | raw e-mail | index | archive | help
This isn't entirely true. rc scripts have a default PATH and HOME. From service(8):
ENVIRONMENT
When used to run rc.d scripts the service command sets HOME to / and PATH
to /sbin:/bin:/usr/sbin:/usr/bin which is how they are set in /etc/rc at
boot time.
Something similar holds true for `cron' as well. I see a lot of unnecessary setting of
absolute paths for binaries that reside in default PATHs.
> ----------------------------------------
> From: Eugene Grosbein <eugen@grosbein.net>
> Sent: Thu Apr 28 11:53:42 CEST 2022
> To: Axel Rau <Axel.Rau@chaos1.de>, <freebsd-hackers@freebsd.org>
> Subject: Re: rc script to let a service wait for db available
>
>
> 28.04.2022 15:55, Axel Rau wrote:
>
> > Ah - yes. Now it calls the script in the background, but there is still an issue.
> > It does not start the server, as it does while calling from the command line.
>
> Generally it means bugs in the startup script: it relies on calling process environment
> like PATH, LANG etc. It must not. It must set needed variables all by itself
> starting from PATH.
>
>
>
--
Sent with https://mailfence.com
Secure and private email
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?187283243.91660.1651167612801>