innobackupex should not assume /usr/bin/perl
Bug #892393 reported by
aeva black
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Fix Released
|
Low
|
Stewart Smith | ||
| 1.6 |
Fix Released
|
Low
|
Stewart Smith | ||
| 2.0 |
Fix Released
|
Low
|
Stewart Smith | ||
Bug Description
On hosts where perl is not installed in /usr/bin/, the innobackup script fails to find a valid interpreter.
[deva@host ]$ innobackupex --apply-log --use-mem=2G ./
bash: /usr/local/
[deva@host ]$ which perl
/usr/local/bin/perl
By comparison, all the percona-toolkit scripts work fine because they begin with:
#!/usr/bin/env perl
instead of:
#!/usr/bin/perl
Related branches
lp://staging/~stewart/percona-xtrabackup/892393-1.6
- Percona developers: Pending requested
-
Diff: 9 lines (+1/-1)1 file modifiedinnobackupex (+1/-1)
| Changed in percona-xtrabackup: | |
| importance: | Undecided → Low |
| status: | New → In Progress |
| assignee: | nobody → Stewart Smith (stewart) |
Revision history for this message
| Brian Fraser (fraserbn) wrote | #1 |
Revision history for this message
| Stewart Smith (stewart) wrote | #2 |
Revision history for this message
| Baron Schwartz (baron-xaprb) wrote | #3 |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #4 |
To post a comment you must log in.
I wonder if using env perl is correct in any case -- for instance, my Linux box didn't have env originally. A nice point of comparison is Tom Christiansen's Unicode::Tussle, particularly the hacks that scripts like unichars ( http://
But this is more of a nitpick than anything, so don't give it too much attention.