Watching something be piped to a file live with tailHow to continue running a program inspite of killing the shell which invoked itLinux terminal, my program only resumes after scrolling the printoutIs there a command in Linux which waits till it will be terminated?Ctrl+c in a sub process is killing a nohup'ed process earlier in the scriptCtrl-C'd an in-place recursive gzip - is this likely to have broken anything?Getting output of another script while preserving line-breakssocat and rich terminal againScript executed as other user from root creates files in wrong directory (root)Dealing with Ctrl+Z in UnixHow to pass Ctrl+C to script called from batch job
How can I determine if the org that I'm currently connected to is a scratch org?
What about the virus in 12 Monkeys?
Is it possible to create a QR code using text?
Intersection Puzzle
Why doesn't using multiple commands with a || or && conditional work?
How does a predictive coding aid in lossless compression?
What method can I use to design a dungeon difficult enough that the PCs can't make it through without killing them?
Im going to France and my passport expires June 19th
How to prevent "they're falling in love" trope
Why are the 737's rear doors unusable in a water landing?
Do scales need to be in alphabetical order?
Should I cover my bicycle overnight while bikepacking?
Avoiding the "not like other girls" trope?
What mechanic is there to disable a threat instead of killing it?
Are there any examples of a variable being normally distributed that is *not* due to the Central Limit Theorem?
Bullying boss launched a smear campaign and made me unemployable
Watching something be piped to a file live with tail
Assassin's bullet with mercury
How do I deal with an unproductive colleague in a small company?
Arrow those variables!
How can I deal with my CEO asking me to hire someone with a higher salary than me, a co-founder?
Would Slavery Reparations be considered Bills of Attainder and hence Illegal?
Is "remove commented out code" correct English?
Alternative to sending password over mail?
Watching something be piped to a file live with tail
How to continue running a program inspite of killing the shell which invoked itLinux terminal, my program only resumes after scrolling the printoutIs there a command in Linux which waits till it will be terminated?Ctrl+c in a sub process is killing a nohup'ed process earlier in the scriptCtrl-C'd an in-place recursive gzip - is this likely to have broken anything?Getting output of another script while preserving line-breakssocat and rich terminal againScript executed as other user from root creates files in wrong directory (root)Dealing with Ctrl+Z in UnixHow to pass Ctrl+C to script called from batch job
I have a python program which is, slowly, generating some output.
I want to capture that in a file, but I also thought I could watch it live with tail.
So in one terminal I'm doing :
python myprog.py > output.txt
and in another terminal :
tail -f output.txt
But it seems like the tail isn't showing me anything while the python program is running. If I hit ctrl-c to kill the python script, suddenly the tail of output.txt starts filling up. But not while the python is running.
What am I doing wrong?
linux command-line pipe
add a comment |
I have a python program which is, slowly, generating some output.
I want to capture that in a file, but I also thought I could watch it live with tail.
So in one terminal I'm doing :
python myprog.py > output.txt
and in another terminal :
tail -f output.txt
But it seems like the tail isn't showing me anything while the python program is running. If I hit ctrl-c to kill the python script, suddenly the tail of output.txt starts filling up. But not while the python is running.
What am I doing wrong?
linux command-line pipe
2
How aboutpython myprog.py | tee output.txt
instead?
– n8te
3 hours ago
@n8te tee might show the same problem if the program isn't flushing the output buffer regularly. This needs flush() and tee.
– JPhi1618
25 mins ago
@JPhi1618 - you could be right but I just tested it with 800MB of data output and it didn't skip a beat.
– n8te
11 mins ago
add a comment |
I have a python program which is, slowly, generating some output.
I want to capture that in a file, but I also thought I could watch it live with tail.
So in one terminal I'm doing :
python myprog.py > output.txt
and in another terminal :
tail -f output.txt
But it seems like the tail isn't showing me anything while the python program is running. If I hit ctrl-c to kill the python script, suddenly the tail of output.txt starts filling up. But not while the python is running.
What am I doing wrong?
linux command-line pipe
I have a python program which is, slowly, generating some output.
I want to capture that in a file, but I also thought I could watch it live with tail.
So in one terminal I'm doing :
python myprog.py > output.txt
and in another terminal :
tail -f output.txt
But it seems like the tail isn't showing me anything while the python program is running. If I hit ctrl-c to kill the python script, suddenly the tail of output.txt starts filling up. But not while the python is running.
What am I doing wrong?
linux command-line pipe
linux command-line pipe
asked 3 hours ago
interstarinterstar
320311
320311
2
How aboutpython myprog.py | tee output.txt
instead?
– n8te
3 hours ago
@n8te tee might show the same problem if the program isn't flushing the output buffer regularly. This needs flush() and tee.
– JPhi1618
25 mins ago
@JPhi1618 - you could be right but I just tested it with 800MB of data output and it didn't skip a beat.
– n8te
11 mins ago
add a comment |
2
How aboutpython myprog.py | tee output.txt
instead?
– n8te
3 hours ago
@n8te tee might show the same problem if the program isn't flushing the output buffer regularly. This needs flush() and tee.
– JPhi1618
25 mins ago
@JPhi1618 - you could be right but I just tested it with 800MB of data output and it didn't skip a beat.
– n8te
11 mins ago
2
2
How about
python myprog.py | tee output.txt
instead?– n8te
3 hours ago
How about
python myprog.py | tee output.txt
instead?– n8te
3 hours ago
@n8te tee might show the same problem if the program isn't flushing the output buffer regularly. This needs flush() and tee.
– JPhi1618
25 mins ago
@n8te tee might show the same problem if the program isn't flushing the output buffer regularly. This needs flush() and tee.
– JPhi1618
25 mins ago
@JPhi1618 - you could be right but I just tested it with 800MB of data output and it didn't skip a beat.
– n8te
11 mins ago
@JPhi1618 - you could be right but I just tested it with 800MB of data output and it didn't skip a beat.
– n8te
11 mins ago
add a comment |
2 Answers
2
active
oldest
votes
You may also need to explicitly flush the buffer for it to get piped upon generation. This is because output is typically only printed when the pipe's buffer fills up (which is in kilobytes I belive), and when the stdin message ends. This is probably to save on read/writes. You could do this after every print, or if you are looping, after the last print within the loop.
import sys
...
print('Some message')
sys.stdout.flush()
New contributor
add a comment |
Instead of trying to tail a live file, use tee
instead. It was made to do exactly what you're trying to do.
From man tee:
tee(1) - Linux man page
Name tee - read from standard input and write to standard output and files
Synopsis
tee [OPTION]... [FILE]...
Description
Copy standard input to each FILE, and also to standard output.
-a, --append
append to the given FILEs, do not overwrite
-i, --ignore-interrupts
ignore interrupt signals
--help
display this help and exit
--version
output version information and exit
If a FILE is -, copy again to standard output.
So in your case you'd run:
python myprog.py | tee output.txt
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "3"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
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
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1421123%2fwatching-something-be-piped-to-a-file-live-with-tail%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
You may also need to explicitly flush the buffer for it to get piped upon generation. This is because output is typically only printed when the pipe's buffer fills up (which is in kilobytes I belive), and when the stdin message ends. This is probably to save on read/writes. You could do this after every print, or if you are looping, after the last print within the loop.
import sys
...
print('Some message')
sys.stdout.flush()
New contributor
add a comment |
You may also need to explicitly flush the buffer for it to get piped upon generation. This is because output is typically only printed when the pipe's buffer fills up (which is in kilobytes I belive), and when the stdin message ends. This is probably to save on read/writes. You could do this after every print, or if you are looping, after the last print within the loop.
import sys
...
print('Some message')
sys.stdout.flush()
New contributor
add a comment |
You may also need to explicitly flush the buffer for it to get piped upon generation. This is because output is typically only printed when the pipe's buffer fills up (which is in kilobytes I belive), and when the stdin message ends. This is probably to save on read/writes. You could do this after every print, or if you are looping, after the last print within the loop.
import sys
...
print('Some message')
sys.stdout.flush()
New contributor
You may also need to explicitly flush the buffer for it to get piped upon generation. This is because output is typically only printed when the pipe's buffer fills up (which is in kilobytes I belive), and when the stdin message ends. This is probably to save on read/writes. You could do this after every print, or if you are looping, after the last print within the loop.
import sys
...
print('Some message')
sys.stdout.flush()
New contributor
New contributor
answered 3 hours ago
DaveyDavey
461
461
New contributor
New contributor
add a comment |
add a comment |
Instead of trying to tail a live file, use tee
instead. It was made to do exactly what you're trying to do.
From man tee:
tee(1) - Linux man page
Name tee - read from standard input and write to standard output and files
Synopsis
tee [OPTION]... [FILE]...
Description
Copy standard input to each FILE, and also to standard output.
-a, --append
append to the given FILEs, do not overwrite
-i, --ignore-interrupts
ignore interrupt signals
--help
display this help and exit
--version
output version information and exit
If a FILE is -, copy again to standard output.
So in your case you'd run:
python myprog.py | tee output.txt
add a comment |
Instead of trying to tail a live file, use tee
instead. It was made to do exactly what you're trying to do.
From man tee:
tee(1) - Linux man page
Name tee - read from standard input and write to standard output and files
Synopsis
tee [OPTION]... [FILE]...
Description
Copy standard input to each FILE, and also to standard output.
-a, --append
append to the given FILEs, do not overwrite
-i, --ignore-interrupts
ignore interrupt signals
--help
display this help and exit
--version
output version information and exit
If a FILE is -, copy again to standard output.
So in your case you'd run:
python myprog.py | tee output.txt
add a comment |
Instead of trying to tail a live file, use tee
instead. It was made to do exactly what you're trying to do.
From man tee:
tee(1) - Linux man page
Name tee - read from standard input and write to standard output and files
Synopsis
tee [OPTION]... [FILE]...
Description
Copy standard input to each FILE, and also to standard output.
-a, --append
append to the given FILEs, do not overwrite
-i, --ignore-interrupts
ignore interrupt signals
--help
display this help and exit
--version
output version information and exit
If a FILE is -, copy again to standard output.
So in your case you'd run:
python myprog.py | tee output.txt
Instead of trying to tail a live file, use tee
instead. It was made to do exactly what you're trying to do.
From man tee:
tee(1) - Linux man page
Name tee - read from standard input and write to standard output and files
Synopsis
tee [OPTION]... [FILE]...
Description
Copy standard input to each FILE, and also to standard output.
-a, --append
append to the given FILEs, do not overwrite
-i, --ignore-interrupts
ignore interrupt signals
--help
display this help and exit
--version
output version information and exit
If a FILE is -, copy again to standard output.
So in your case you'd run:
python myprog.py | tee output.txt
answered 2 hours ago
n8ten8te
5,17272234
5,17272234
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1421123%2fwatching-something-be-piped-to-a-file-live-with-tail%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
How about
python myprog.py | tee output.txt
instead?– n8te
3 hours ago
@n8te tee might show the same problem if the program isn't flushing the output buffer regularly. This needs flush() and tee.
– JPhi1618
25 mins ago
@JPhi1618 - you could be right but I just tested it with 800MB of data output and it didn't skip a beat.
– n8te
11 mins ago