Re: [Discuss-gnuradio] Daemonizing a flowgraph

2017-07-12 Thread Dan CaJacob
Marcus' suggestions are great. In the past, I have also used supervisord to "daemonize" a flowgraph. If it ever dies, supervisord brings it right back if that's what you want. It's like systemd for python, kinda. On Wed, Jul 12, 2017 at 3:30 AM Marcus Müller wrote: > Oh, by the way, maybe you, i

Re: [Discuss-gnuradio] Daemonizing a flowgraph

2017-07-12 Thread Marcus Müller
Oh, by the way, maybe you, instead, simply would want to run your whole flowgraph using `nohup`, or simply in a `screen` or `tmux` session :) On 07/12/2017 09:22 AM, Marcus Müller wrote: > > If you can, update to the most current UHD – we've worked on the > logging infrastructure, and you can sim

Re: [Discuss-gnuradio] Daemonizing a flowgraph

2017-07-12 Thread Marcus Müller
If you can, update to the most current UHD – we've worked on the logging infrastructure, and you can simply disable that. This will probably require building both UHD, and as soon as you've done that, GNU Radio from source. Best regards, Marcus On 07/11/2017 10:39 PM, devin kelly wrote: > Hello,

[Discuss-gnuradio] Daemonizing a flowgraph

2017-07-11 Thread devin kelly
Hello, I have a flowgraph that I made with GRC and modified. All I want to do with the flowgraph is make it run as a daemon. I understand that if there are overflows or underflows I'll miss them, that's OK. I added some basic python code to daemonize my flowgraph: # Fork once