Van: bob prohaska
Datum: 17 juni 2021 03:47
Aan: FreeBSD ports
Onderwerp: Re: Restarting poudriere
On Tue, Jun 15, 2021 at 01:31:32AM -0700, Mark Millard wrote:
>
> Bob has a history of posting large log files someplace for
> reference. So I'd not be surprised if he does
On Tue, Jun 15, 2021 at 01:31:32AM -0700, Mark Millard wrote:
>
> Bob has a history of posting large log files someplace for
> reference. So I'd not be surprised if he does that again for
> this issue at some point.
>
Is it feasible to set up a poudriere working directory under a
public_html ind
On 2021-Jun-15, at 02:20, Michael Gmelin wrote:
> On Tue, 15 Jun 2021 01:31:32 -0700
> Mark Millard wrote:
>
>> Michael Gmelin wrote on
>> Date: Tue, 15 Jun 2021 09:31:26 +0200 :
>>
>> On Mon, 14 Jun 2021 18:02:33 -0700
>> bob prohaska wrote:
>>>
On Mon, Jun 14, 2021 at 09:52:22PM +020
On Tue, 15 Jun 2021 01:31:32 -0700
Mark Millard wrote:
> Michael Gmelin wrote on
> Date: Tue, 15 Jun 2021 09:31:26 +0200 :
>
> On Mon, 14 Jun 2021 18:02:33 -0700
> bob prohaska wrote:
> >
> > > On Mon, Jun 14, 2021 at 09:52:22PM +0200, Michael Gmelin wrote:
> > > >
> > > >
> > >
Michael Gmelin wrote on
Date: Tue, 15 Jun 2021 09:31:26 +0200 :
On Mon, 14 Jun 2021 18:02:33 -0700
bob prohaska wrote:
>
> > On Mon, Jun 14, 2021 at 09:52:22PM +0200, Michael Gmelin wrote:
> > >
> > >
> > > > On 14. Jun 2021, at 20:30, bob prohaska
> > > > wrote:
> > > >
> > > > ???On M
On Mon, 14 Jun 2021 18:02:33 -0700
bob prohaska wrote:
> On Mon, Jun 14, 2021 at 09:52:22PM +0200, Michael Gmelin wrote:
> >
> >
> > > On 14. Jun 2021, at 20:30, bob prohaska
> > > wrote:
> > >
> > > ???On Mon, Jun 14, 2021 at 06:46:52PM +0200, Michael Gmelin
> > > wrote:
> > >> On Mon
poudriere adds DISABLE_MAKE_JOBS=poudriere to make.conf by default.
ALLOW_MAKE_JOBS and ALLOW_MAKE_JOBS_PACKAGES in poudriere.conf, turn it off.
On Mon, Jun 14, 2021 at 09:52:22PM +0200, Michael Gmelin wrote:
>
>
> > On 14. Jun 2021, at 20:30, bob prohaska wrote:
> >
> > ???On Mon, Jun 14, 2021 at 06:46:52PM +0200, Michael Gmelin wrote:
> >> On Mon, 14 Jun 2021 09:28:39 -0700
> >> What do you mean by "restarting"?
> >> How do you invoke
> On 14. Jun 2021, at 20:30, bob prohaska wrote:
>
> On Mon, Jun 14, 2021 at 06:46:52PM +0200, Michael Gmelin wrote:
>> On Mon, 14 Jun 2021 09:28:39 -0700
>> What do you mean by "restarting"?
>> How do you invoke poudriere exactly?
> As root,
> poudriere bulk -J 2 -j main x11-wm/lxqt www/chro
On 2021-Jun-14, at 12:03, Mark Millard wrote:
> bob prohaska wrote on
> Date: Mon, 14 Jun 2021 09:28:39 -0700 :
>
>> Thanks to much support on the lists it looks like poudriere _almost_
>> worked on the Pi3.
>
> I'm presuming the RPi3B+ is being used as aarch64 instead
> of armv7.
>
>> In
bob prohaska wrote on
Date: Mon, 14 Jun 2021 09:28:39 -0700 :
> Thanks to much support on the lists it looks like poudriere _almost_
> worked on the Pi3.
I'm presuming the RPi3B+ is being used as aarch64 instead
of armv7.
> In earlier tries builds of llvm10 failed from lack of memory. Restrain
On Mon, Jun 14, 2021 at 06:46:52PM +0200, Michael Gmelin wrote:
>
>
> On Mon, 14 Jun 2021 09:28:39 -0700
>
> What do you mean by "restarting"?
> How do you invoke poudriere exactly?
>
As root,
poudriere bulk -J 2 -j main x11-wm/lxqt www/chromium > testbuild.log
Sorry for the omission, thanks f
On Mon, 14 Jun 2021 09:28:39 -0700
bob prohaska wrote:
> Thanks to much support on the lists it looks like poudriere _almost_
> worked on the Pi3.
>
> In earlier tries builds of llvm10 failed from lack of memory.
> Restraining poudriere with -J 2 and MAKE_JOBS_NUMBER=2 in
> /etc/make.conf, a
Thanks to much support on the lists it looks like poudriere _almost_
worked on the Pi3.
In earlier tries builds of llvm10 failed from lack of memory. Restraining
poudriere with -J 2 and MAKE_JOBS_NUMBER=2 in /etc/make.conf, along with
turning off use of tmpfs appears to have relieved the excess m
Moin!
Best guide is run 'poudriere bulk’ under tmux or screen session to keep it
running while session detached.
About restart pou build session you need to know name of failed build
(something like '2021-06-09_17h55m20s’) and start a build with -B
2021-06-09_17h55m20s (for example) param to r
As for why Ctrl+Z suspend doesn't work, perhaps
poudriere-3.3.6/src/poudriere-sh/helpers.c is trapping it.
However, it does trap SIGTSTP, but not SIGSTOP.
In other words, Ctrl+Z with SIGTSTP will not suspend, but SIGSTOP will.
I actually used the following method to suspend it.
# Find the jail
jl
.
I do use sysutils/tmux when I connect from my laptop to my package
baking system where poudriere runs. It makes it easy to detach and go
away with the laptop to other locations while poudriere is doing its
job.
Re/ stopping/restarting poudriere, it would be enough for most of the
cases (at least fo
Greg Rivers via freebsd-ports wrote on 2021/06/09 10:05:
> Even better, run your sessions from within sysutils/tmux or sysutils/screen.
I also sometimes use poudriere on tmux for when I want to shutdown X.
On Tuesday, 8 June 2021 20:05:41 CDT Greg Rivers wrote:
> Even better, run your sessions from within sysutils/tmux or sysutils/screen.
>
Oh, and also check out net/mosh.
--
Greg
On Tuesday, 8 June 2021 19:36:51 CDT Kevin P. Neal wrote:
> On Tue, Jun 08, 2021 at 04:29:54PM -0700, bob prohaska wrote:
> > For now, it seems the answer is "Let poudriere finish!".
>
> I have issues with my ISP where my ssh sessions die at random times, usually
> (but not always) when I'm away f
On Wed, Jun 09, 2021 at 07:47:29AM +1000, Dave Horsfall wrote:
> On Tue, 8 Jun 2021, bob prohaska wrote:
>
> > More generally, can a poudriere session be gracefully stopped, say for
> > maintenance work or to run a more urgent job, and then restarted without
> > loss of intermediate work?
>
> Wel
/usr/local/share/poudriere/common.sh has trap '' SIGTSTP.
Probably all ^Z will be handled by this.
I shoot kill -USR1 etc. at jobs that take a long time and make them fail on
purpose :)
On Tue, 8 Jun 2021, bob prohaska wrote:
More generally, can a poudriere session be gracefully stopped, say for
maintenance work or to run a more urgent job, and then restarted without
loss of intermediate work?
Well, there's ^Z depending upon what you want to do in the meantime...
-- Dave
On 2021-Jun-8, at 10:54, Mark Millard wrote:
>
> bob prohaska wrote on
> Date: Tue, 8 Jun 2021 07:56:24 -0700 :
>
>> Is it possible to restart a poudriere build session so it picks up
>> where it left off?
>>
>> I mistakenly hit a control-c in the controlling terminal of a long
>> build and w
bob prohaska wrote on
Date: Tue, 8 Jun 2021 07:56:24 -0700 :
> Is it possible to restart a poudriere build session so it picks up
> where it left off?
>
> I mistakenly hit a control-c in the controlling terminal of a long
> build and would like to restart it with minimum lost work.
Packages th
On Tue, 8 Jun 2021 17:44:16 +0200, Kurt Jaeger wrote:
> Hi!
>
>> Is it possible to restart a poudriere build session so it picks up
>> where it left off?
>
> I don't think so.
>
Maybe stopping the system completely with the kernel debugger and resume
excecution the other day.
--
Matthias Apitz
Hi!
> Is it possible to restart a poudriere build session so it picks up
> where it left off?
I don't think so.
--
p...@opsec.eu+49 171 3101372Now what ?
Is it possible to restart a poudriere build session so it picks up
where it left off?
I mistakenly hit a control-c in the controlling terminal of a long
build and would like to restart it with minimum lost work.
More generally, can a poudriere session be gracefully stopped,
say for maintenance w
28 matches
Mail list logo
