Maybe someone can open up one of the deep PD-Linux mysteries for me...
What is PD watchdog, and how can I get him to stop barking?
I understand that, when running PD in realtime/root mode, you have higher priority in the system, and that this priority is enough to slow or even stop other processes when PD uses too much resource. I imagine "pd watchdog" is a systems monitor who barks when PD uses too much CPU. However, running rt/root, it seems he *always* barks at me, even when using only 50% CPU. The barking isn't so bad, but the sluggish response time of the computer and espc the GUI is!
In short, root/realtime mode is just too piggish sometimes.
I know that with Jack, there is a way to do non-root realtime priority by making a "capabilities" patch to the kernel. Does something similar exist for PD? And if so, would non-root realtime priority be "safer", and thus shut the dogs up, and keep a responsive computer?
thx, d.
Answering my own posts again... isn't it lovely to see someone else's thought processes in motion? ;-)
Anyway... I thought I remembered some discussion a while back on this topic, so an archive-hunt turned up a source patch for PD. I'll try this later, but can I ask Guenter.... did this not make it into CVS or normal PD 0.37.1 release?
d.
On Sun, 18 Jan 2004, Michal Seta wrote:
Hi all,
I've been experiencing a problem with running pd -rt -jack for some time now. After starting pd I get:
watchdog: signaling pd...
and of course pd doesn't respond to any commands. At some point I thought the problem was gone but it isn't.
Hi,
I couldn't reproduce until now, because my SBLive has a minimum latency setting of 512 samples.
Now, using the playback only trick I got down to 256 and ... I have the same behaviour.
I had this problem fixed in CVS once, but it seems that it got changed back, but it is quite easy to fix:
in s_inter.c, in the function sys_set_priority(int higher) change the line
p3 = (higher ? p2 - 1 : p2 - 3);
to
p3 = (higher ? p1 + 3 : p1 + 1);
.. let me know if it works
Thanks for reporting,
Guenter
PS: I will update the CVS as soon as sourceforge lets m
Hallo, derek holzer hat gesagt: // derek holzer wrote:
Answering my own posts again... isn't it lovely to see someone else's thought processes in motion? ;-)
Anyway... I thought I remembered some discussion a while back on this topic, so an archive-hunt turned up a source patch for PD. I'll try this later, but can I ask Guenter.... did this not make it into CVS or normal PD 0.37.1 release?
It's in the latest MSP Pd, slightly modified, but works here. In general, would not run pd as root, but I have it "chmod +s" on my boxes. That way, Pd can drop root privileges after it got itself the realtime scheduling stuff done. This is more secure in the end than running as root (which cannot be "dropped"). You can restrict access to pd by using the group permissions.
ciao
Frank Barknecht _ ______footils.org__
On Thu, 18 Mar 2004, derek holzer wrote:
Answering my own posts again... isn't it lovely to see someone else's thought processes in motion? ;-)
Anyway... I thought I remembered some discussion a while back on this topic, so an archive-hunt turned up a source patch for PD. I'll try this later, but can I ask Guenter.... did this not make it into CVS or normal PD 0.37.1 release?
Yes, it surely is included in the devel_0_37 branch. The watchdog should not bark at 50%, so there is something wrong. Did you take a look at the system performance with top ? Probably there are other processes that eat up all you CPU ? Does this happen always or just with a specific patch ? Are you using jack ? (more questions than answers, I know)
Guenter
d.
On Sun, 18 Jan 2004, Michal Seta wrote:
Hi all,
I've been experiencing a problem with running pd -rt -jack for some time now. After starting pd I get:
watchdog: signaling pd...
and of course pd doesn't respond to any commands. At some point I thought the problem was gone but it isn't.
Hi,
I couldn't reproduce until now, because my SBLive has a minimum latency setting of 512 samples.
Now, using the playback only trick I got down to 256 and ... I have the same behaviour.
I had this problem fixed in CVS once, but it seems that it got changed back, but it is quite easy to fix:
in s_inter.c, in the function sys_set_priority(int higher) change the line
p3 = (higher ? p2 - 1 : p2 - 3);
to
p3 = (higher ? p1 + 3 : p1 + 1);
.. let me know if it works
Thanks for reporting,
Guenter
PS: I will update the CVS as soon as sourceforge lets m
-- derek holzer ::: http://www.umatic.nl ---Oblique Strategy # 51: "Distorting time"
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
-
derek holzer -
Frank Barknecht -
guenter geiger