Bug 118125 - sudo runs commands with wrong stdout
Summary: sudo runs commands with wrong stdout
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: sudo
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks: FC2Blocker
TreeView+ depends on / blocked
 
Reported: 2004-03-12 06:58 UTC by Aleksey Nogin
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-03-17 16:25:12 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Aleksey Nogin 2004-03-12 06:58:41 UTC
Sudo recently started redirecting the stdout of the commands somewhere
else.

It works correctly on Fedora Core 1:

% /usr/bin/sudo echo foo > /dev/null
% rpm -q sudo
sudo-1.6.7p5-2

But fails in Raw Hide:

% /usr/bin/sudo echo foo > /dev/null
foo
% sudo-1.6.7p5-18

P.S. really annoying - for example, things like

sudo grep something /var/log/something | less

no longer work as expected :-(

Comment 1 Thomas Woerner 2004-03-15 09:58:29 UTC
I can not reproduce this bug:

$ /usr/bin/sudo echo foo > /dev/null
$ rpm -q sudo
sudo-1.6.7p5-18
$ 

$ sudo grep kernel /var/log/messages | less
Works, too.

Do you have any special settings for root?


Comment 2 Aleksey Nogin 2004-03-15 19:46:38 UTC
> Do you have any special settings for root?

I do not believe so.

Comment 3 Nils Philippsen 2004-03-16 10:35:25 UTC
Perhaps this is some shell issue. From the prompt, it looks like you,
Aleksey use csh/tcsh while Thomas uses bash. Is it like this?

Comment 4 Aleksey Nogin 2004-03-16 11:09:56 UTC
Yes, I use tcsh, but the root's shell is still bash.

Comment 5 Thomas Woerner 2004-03-16 16:01:56 UTC
This is an error in the SElinux patch for sudo.

Comment 7 Thomas Woerner 2004-03-17 16:24:59 UTC
Fixed in rawhide in rpm sudo-1.6.7p5-20 or newer.

Comment 8 Aleksey Nogin 2004-03-18 03:52:46 UTC
Confirming fixed.


Note You need to log in before you can comment on or make changes to this bug.