Date: Fri, 24 Apr 2015 07:00:20 +0200 From: Michael Schuster <michaelsprivate@gmail.com> To: Andrea Venturoli <ml@netfence.it> Cc: questions <questions@freebsd.org> Subject: Re: Bacula and perl 5.20 Message-ID: <CADqw_gLNQ%2Brm3zRNJEROE260SN8Tb6MuzfaOsaZoQkyn=oiU_Q@mail.gmail.com> In-Reply-To: <553893FE.8090601@netfence.it> References: <5538919D.8060507@netfence.it> <CADqw_g%2BryZrFG7JFEKLHkDsOWY-ZOy5wKRba%2Bb6e9AcgebuEig@mail.gmail.com> <553893FE.8090601@netfence.it>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Apr 23, 2015 at 8:41 AM, Andrea Venturoli <ml@netfence.it> wrote: > On 04/23/15 08:32, Michael Schuster wrote: > >> Hi, >> > > Hello. > > > > you need to tell people (no, not me in private ;-), what "stop working" >> looks like in detail. >> > > Right, sorry. > In the logs I get: > >> BeforeJob: env: perl: No such file or directory >> > > Running "env perl" from the command line seems to work however. > what does that mean in detail? what does "which perl" print out? I'd suggest that for a test, you replace your script with a simple one that does ----- begin which perl echo $PATH ----- end (make it executable!) and see what it does if you call it the same way you usuall call your script > A guess: is /usr/local/bin in your standard PATH (or rather, the path >> that the script sees)? >> > > In my path: yes. > In the script path: I don't know. > > I now realize that 5.20 does not install "/usr/bin/perl", which was an > option (which I had enabled) in 5.16. > HTH -- Michael Schuster http://recursiveramblings.wordpress.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADqw_gLNQ%2Brm3zRNJEROE260SN8Tb6MuzfaOsaZoQkyn=oiU_Q>