Could it be the difference in $PATH between the 2 commands?
On Fri, 2002-05-31 at 14:38, Oleg wrote:
Hi
The only way I can get mplayer to work as well as or better than its Windows
counterpart on my hardware is by using -vo xvidix option that requires
superuser privileges, so I added
On Saturday 01 June 2002 12:04 am, Ron Johnson wrote:
Could it be the difference in $PATH between the 2 commands?
What do you mean? There's only one executable 'mplayer' and only one 'sudo'.
I also added /usr/bin/id to the list of commands I can run as root, and it
printed uid=0(root)
On Sat, Jun 01, 2002 at 12:43:49AM -0400, Oleg wrote:
On Saturday 01 June 2002 12:04 am, Ron Johnson wrote:
Could it be the difference in $PATH between the 2 commands?
What do you mean? There's only one executable 'mplayer' and only one 'sudo'.
He means that sudo sets a hard-coded $PATH
What do you mean? There's only one executable 'mplayer' and only one 'sudo'.
He means that sudo sets a hard-coded $PATH (defined at compile time) and su
sets a potentially different one derived from any of several places.
A similar alternative (to the original question) is that it could be
Hi
The only way I can get mplayer to work as well as or better than its Windows
counterpart on my hardware is by using -vo xvidix option that requires
superuser privileges, so I added
oleg ALL = (root) NOPASSWD: /usr/local/bin/mplayer *
to /etc/sudoers. Now sudo mplayer -vo xvidix file_name
5 matches
Mail list logo
