sleep 120 and tinderbox
Muhammad Moinur Rahman
5u623l20 at gmail.com
Sat May 5 04:32:12 EDT 2012
Thanks for the info. I have tried restarting the service stopping the
service and starting the service again. Seems like I have a solution for
the problem. There is a file named tinderdlock in each of the builds
directory. Removing the file solves the problem.
On Sat, May 5, 2012 at 2:54 AM, Dominic Fandrey <kamikaze at bsdforen.de>wrote:
> On 04/05/2012 17:12, Muhammad Moinur Rahman wrote:
>> I was running my Tinderbox fine until I made a mistake of adding an
>> port to the queue. Now I can see that all the tinderd process has a child
>> process of "sleep 120". I have tried restarting the service and restarting
>> the host. But still no luck. Whenever it comes up it comes up with those
>> child processes.
> Well, I don't know how to fix the problem, but using the rc.d
> script you can kill them all.
> A: Because it fouls the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing on usenet and in e-mail?
More information about the tinderbox-list