Date: Tue, 10 Feb 2009 21:07:56 +0100 From: Torfinn Ingolfsen <tingox@gmail.com> To: freebsd-ports@freebsd.org Cc: Ion-Mihai Tetcu <itetcu@freebsd.org> Subject: Re: tinderbox - tinderd and nullfs? Message-ID: <ef8c8a880902101207l3aeb043anb59ab6f1b45d0f90@mail.gmail.com> In-Reply-To: <20090210020050.6f160713@it.buh.tecnik93.com> References: <ef8c8a880901161421p712bcfccrd496d38b19ef87d2@mail.gmail.com> <49413692@ipt.ru> <ef8c8a880901180337q423a3fd5g57d222f8d3818140@mail.gmail.com> <20090118222145.6ff13615@it.buh.tecnik93.com> <ef8c8a880902091400t14cc30a3x7aa570bd2b12c2ad@mail.gmail.com> <20090210020050.6f160713@it.buh.tecnik93.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, On Tue, Feb 10, 2009 at 1:00 AM, Ion-Mihai Tetcu <itetcu@freebsd.org> wrote: > ps axw > mount Actually, it did eventually build. The reason for the time was that it built 77 ports (dependencies?) in that run. So, tinderbuild works. Restarting tinderd didn't have any effect - the job in the tinderd queue still didn't move, and nothing happened to tinderd. Howevr, I deleted that job (from the web ui), and re-scheduled the same port (also from the web ui). This time it worked without problems. Perhaps the minor upgrade from tinderbox 3.1.2_1 to 3.1.2_2 fixed the problem? Anyway, it works now. Thanks to everyone for their help. > If you use reply all there are better chances the other people that > replied to your email get your message in front of their ayes ;-) Well, IMHO such practice is a bit "intrusive" unless a person have explicitly asked to be copied (or I really, really want to get that person's attention). So I'll risk it. :-) After all, this is a mailing list - interested parties are supposed to to read it, right? (I made an exception for you this time) -- Regards, Torfinn Ingolfsen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ef8c8a880902101207l3aeb043anb59ab6f1b45d0f90>