I think that cron.d directory works a bit different, as username is specified in argument after time.
Yep, tested that. So, it's not using variables from /etc/crontab -- Eero 2015-10-22 23:09 GMT+03:00 Reindl Harald <[email protected]>: > > > Am 22.10.2015 um 21:58 schrieb Eero Volotinen: > >> You should really read man page of cron(tab). Variables are defined >> inside the file scope, they are not global. >> > > that's pure nonsense and i can prove that by 10 years Redhat / Fedora > expierience setting all sorts of environment varibales inside /etc/crontab > including the PATH and *as long* not some crap overrides that by intention > they are used by *anything* started via crond > > 2015-10-22 22:52 GMT+03:00 Diego Gomes <[email protected] >> <mailto:[email protected]>>: >> >> # cat /etc/crontab >> SHELL=/bin/bash >> PATH=/sbin:/bin:/usr/sbin:/usr/bin >> MAILTO=root >> HOME=/ >> >> already have! >> >> what is inside of cron.d does not respect the PATH from /etc/crontab >> > > > _______________________________________________ > Openvas-discuss mailing list > [email protected] > https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss >
_______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
