OK, thanks. There doesn't seem to be anything to do in man-db, in that
case, but let us know (reopening the bug) if that's wrong.
** Changed in: man-db (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
lundi 5 août 2019 11:40
À : th...@thibs.com
Objet : [Bug 1828947] Re: Absolute path missing in cron files
What does /etc/crontab say? On my system it has:
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
--
You received this bug notification because you are subscribed to t
What does /etc/crontab say? On my system it has:
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828947
Title:
Absolute path missin
Hello,
It was on a brand-new installation without any customisation. You're
right those path should be specified in $PATH
Best Regards
Thibault
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828947
It would be contrary to policy to use explicit paths here. Why isn't
your cron daemon running these scripts with /sbin already in $PATH? It
ought to be, and that's where the problem is here, not in man-db.
** Changed in: man-db (Ubuntu)
Status: New => Incomplete
--
You received this bug
