| To: | Tomas Dohnalek <tdohnale@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] qa - use of read when pipelining sudo command |
| From: | Nathan Scott <nathans@xxxxxxxxxx> |
| Date: | Thu, 4 Oct 2012 05:44:41 -0400 (EDT) |
| Cc: | pcp@xxxxxxxxxxx |
| In-reply-to: | <506D53EA.8050304@xxxxxxxxxx> |
| Reply-to: | Nathan Scott <nathans@xxxxxxxxxx> |
----- Original Message ----- > Hi, > in the beginning I would like to show the way I am running > test-cases. > > # scl enable devtoolset-1.1 bash (are you root at this point?) > # su -c "./check 110" pcpqa > FWIW, I tend to do: $ sudo su - pcpqa $ ./check ... > This indicates to me, that the "both, daemon, socket" didn't "get > through" to sudo Install command. It looks a bit like its closing stdin at some point, and the piped in text is being dropped on the floor. Not sure where/why though. > If I rewrite it this way > > $sudo "echo 'both > daemon > socket' | ./Install -e" >>$tmp.out 2>&1 > > It's working then. Any suggestions what is wrong? > Its a wierd one, not really sure, sorry. cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [pcp] qa - use of read when pipelining sudo command, Tomas Dohnalek |
|---|---|
| Next by Date: | Re: [pcp] qa - use of read when pipelining sudo command, Tomas Dohnalek |
| Previous by Thread: | [pcp] qa - use of read when pipelining sudo command, Tomas Dohnalek |
| Next by Thread: | Re: [pcp] qa - use of read when pipelining sudo command, Tomas Dohnalek |
| Indexes: | [Date] [Thread] [Top] [All Lists] |