Capture data going through named pipe

Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
Is there a practical and easy way to capture data going through a named pipe? I've tried wireshark, but it only accepts a specific data format. I've also tried cat, but I get mixed results.
Thank you
pipe fifo
add a comment |Â
up vote
1
down vote
favorite
Is there a practical and easy way to capture data going through a named pipe? I've tried wireshark, but it only accepts a specific data format. I've also tried cat, but I get mixed results.
Thank you
pipe fifo
Have you thought oftee?
â X Tian
Mar 7 at 11:37
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
Is there a practical and easy way to capture data going through a named pipe? I've tried wireshark, but it only accepts a specific data format. I've also tried cat, but I get mixed results.
Thank you
pipe fifo
Is there a practical and easy way to capture data going through a named pipe? I've tried wireshark, but it only accepts a specific data format. I've also tried cat, but I get mixed results.
Thank you
pipe fifo
asked Mar 7 at 11:34
yhu420
63
63
Have you thought oftee?
â X Tian
Mar 7 at 11:37
add a comment |Â
Have you thought oftee?
â X Tian
Mar 7 at 11:37
Have you thought of
tee ?â X Tian
Mar 7 at 11:37
Have you thought of
tee ?â X Tian
Mar 7 at 11:37
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
0
down vote
I would set up two named pipes and connect them with
tee -a pipe.log < pipe1 > pipe2
Then have the first app write to pipe1 and the second read from pipe2.
Alternatively you could connect them with
tee pipe2 < pipe1
To have the data piped to your stdout.
add a comment |Â
up vote
0
down vote
accepted
Nevermind, I found out how to read the data using shell scripts as described here:
http://www.linuxjournal.com/content/using-named-pipes-fifos-bash
while true
do
if read line <$pipe; then
if [[ "$line" == 'quit' ]]; then
break
fi
echo $line
fi
done
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
I would set up two named pipes and connect them with
tee -a pipe.log < pipe1 > pipe2
Then have the first app write to pipe1 and the second read from pipe2.
Alternatively you could connect them with
tee pipe2 < pipe1
To have the data piped to your stdout.
add a comment |Â
up vote
0
down vote
I would set up two named pipes and connect them with
tee -a pipe.log < pipe1 > pipe2
Then have the first app write to pipe1 and the second read from pipe2.
Alternatively you could connect them with
tee pipe2 < pipe1
To have the data piped to your stdout.
add a comment |Â
up vote
0
down vote
up vote
0
down vote
I would set up two named pipes and connect them with
tee -a pipe.log < pipe1 > pipe2
Then have the first app write to pipe1 and the second read from pipe2.
Alternatively you could connect them with
tee pipe2 < pipe1
To have the data piped to your stdout.
I would set up two named pipes and connect them with
tee -a pipe.log < pipe1 > pipe2
Then have the first app write to pipe1 and the second read from pipe2.
Alternatively you could connect them with
tee pipe2 < pipe1
To have the data piped to your stdout.
answered Mar 7 at 12:05
couling
228210
228210
add a comment |Â
add a comment |Â
up vote
0
down vote
accepted
Nevermind, I found out how to read the data using shell scripts as described here:
http://www.linuxjournal.com/content/using-named-pipes-fifos-bash
while true
do
if read line <$pipe; then
if [[ "$line" == 'quit' ]]; then
break
fi
echo $line
fi
done
add a comment |Â
up vote
0
down vote
accepted
Nevermind, I found out how to read the data using shell scripts as described here:
http://www.linuxjournal.com/content/using-named-pipes-fifos-bash
while true
do
if read line <$pipe; then
if [[ "$line" == 'quit' ]]; then
break
fi
echo $line
fi
done
add a comment |Â
up vote
0
down vote
accepted
up vote
0
down vote
accepted
Nevermind, I found out how to read the data using shell scripts as described here:
http://www.linuxjournal.com/content/using-named-pipes-fifos-bash
while true
do
if read line <$pipe; then
if [[ "$line" == 'quit' ]]; then
break
fi
echo $line
fi
done
Nevermind, I found out how to read the data using shell scripts as described here:
http://www.linuxjournal.com/content/using-named-pipes-fifos-bash
while true
do
if read line <$pipe; then
if [[ "$line" == 'quit' ]]; then
break
fi
echo $line
fi
done
answered Mar 7 at 12:07
yhu420
63
63
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f428724%2fcapture-data-going-through-named-pipe%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Have you thought of
tee?â X Tian
Mar 7 at 11:37