Project

General

Profile

Actions

Bug #2049

closed

env(1) should print program it attempts to exec on error, not argv[0]

Added by Albert Lee over 9 years ago. Updated about 9 years ago.

Status:
Resolved
Priority:
Low
Category:
cmd - userland programs
Start date:
2012-01-31
Due date:
% Done:

100%

Estimated time:
Difficulty:
Bite-size
Tags:
Gerrit CR:

Description

If env is passed a command (utility in the manpage) which it is unable to execute, it currently prints unhelpful and misleading error messages like "/usr/bin/env: No such file or directory" for ENOENT. It should be including the pathname that failed.

Actions #1

Updated by Albert Lee over 9 years ago

  • Assignee set to Robert Mustacchi

Thanks for volunteering. :)

Actions #2

Updated by Robert Mustacchi over 9 years ago

Current behavior:

$ /usr/bin/env foobar
/usr/bin/env: No such file or directory

New behavior:

$ ./usr/bin/env foobar
./usr/bin/env: foobar: No such file or directory
Actions #3

Updated by Robert Mustacchi about 9 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100
  • Tags deleted (needs-triage)

Resolved in 13707:3f41b24ce657.

Actions

Also available in: Atom PDF