Can't exec "id" errors from pg_maintenance after upgrading to 87ubuntu1
Bug #422189 reported by
James Troup
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
postgresql-common (Ubuntu) |
Invalid
|
Medium
|
Martin Pitt | ||
Hardy |
Fix Released
|
High
|
Martin Pitt |
Bug Description
Binary package hint: postgresql-common
After upgrading to 87ubuntu1 on our servers, I'm getting the following cron spam, presumably because $PATH is not set in cron and the script doesn't use the full path to the binary.
| From: <email address hidden> (Cron Daemon)
| Subject: Cron <root@druzhnaya> if [ -x /usr/sbin/
| To: <email address hidden>
| X-Sent: 12 minutes ago
|
| Can't exec "id": No such file or directory at /usr/share/
| Use of uninitialized value in concatenation (.) or string at /usr/share/
Related branches
tags: |
added: verification-done removed: verification-needed |
To post a comment you must log in.
12:20 < slangasek> elmo: <blink> is /usr/bin not in the path?
12:20 < elmo> slangasek: not in a cron job, no
12:21 < slangasek> hrm
12:21 < elmo> not unless the cron file goes to the trouble of setting $PATH
12:21 < elmo> /etc/crontab sets PATH, but postgresql-common is in /etc/cron.d