StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POPipe Find command "stderr" to a command
primarykey
Id
9515367
data
AcceptedAnswerId
9518008
AnswerCount
3
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-03-01T11:30:15.903
FavoriteCount
0
LastActivityDate
2012-03-02T13:36:44.800
LastEditDate
2012-03-02T08:59:50.127
LastEditorUserId
851818
OwnerUserId
851818
ParentId
0
PostTypeId
1
Score
3
ViewCount
2927
LastEditorDisplayName
text
Body
Hi I have a peculiar problem and I'm trying hard to find (pun intended) a solution for it. <pre><code>$> find ./subdirectory -type f 2>>error.log </code></pre> I get an error, something like, "find: ./subdirectory/noidea: Permission denied" from this command and this will be redirected to error.log. Is there any way I can pipe the stderr to another command before the redirection to error.log? I want to be able to do something like <pre><code>$> find ./subdirectory -type f 2 | sed "s#$.*$#${PWD}\1#" >> error.log </code></pre> where I want to pipe only the stderr to the sed command and get the whole path of the find command error. I know piping doesn't work here and is probably not the right way to go about. My problem is I need both the stdout and stderr and the both have to be processed through different things simultaneously. EDIT: Ok. A slight modification to my problem. Now, I have a shell script, solve_problem.sh In this shell script, I have the following code <pre><code>ErrorFile="error.log" for directories in `find ./subdirectory -type f 2>> $ErrorFile` do field1=`echo $directories | cut -d / -f2` field2=`echo $directories | cut -d / -f3` done </code></pre> Same problem but inside a shell script. The "find: ./subdirectory/noidea: Permission denied" error should go into $ErrorFile and stdout should get assigned to the variable $directories.
Tags
<unix><find><pipe><io-redirection>
Title
Pipe Find command "stderr" to a command
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USlatestVersion
UserOwnerUserId
1. USlatestVersion
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POPipe Find command "stderr" to a command
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POPipe Find command "stderr" to a command
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 POPipe Find command "stderr" to a command
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.