Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

19
  • 1
    You start it from init, yet it produces output to the screen? Processes started via init should be daemons and produce no output. Can you explain more about where the output goes, when, and why? And please include your init script. Commented Apr 1, 2014 at 14:05
  • Obviously this is not the case for other init process, and since it is also not the case in general for others, you need to provide a reproducible example if you want an answer. @Mikel Note he used that "for example" -- even if the process does print to the screen, it should not be slowed down particular except to the extent that it is interleaved with other processes. Commented Apr 1, 2014 at 14:10
  • @TAFKA Sure. But how it prints to the screen could be an important piece of the puzzle. Does it print to /dev/console? Directly or via syslog for example? What does it try to print and when? We don't have any information. Commented Apr 1, 2014 at 14:17
  • @Mikel The line in init.d calls the python script I have edited above. This runs in the background, I can connect to the application when it is running. The application is a software router. I connect to it's console. Here is where all the slow output is observed Commented Apr 1, 2014 at 14:20
  • 'If there is information being printed to the screen for example, it will be printed out in chunks.' This sounds like the normal buffering you get when a program doesn't output to a terminal. Perhaps you are just looking for the program to be line buffered so that each line is output immediately (or completely unbuffered). Maybe the reason you think it is slow is just because the output is left in buffer for a while. How is it that you see output when the program is started by an init script? Commented Apr 1, 2014 at 14:55