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
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 ?
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
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 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
> Hi all,
>
> I have just submitted two port updates (and maintainer change) for
> hllib and hlextract.
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256249
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256250
>
> This was mainly in preparation for my port of Half-Life. Which is
> bas
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
/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 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
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 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
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.
El día martes, junio 08, 2021 a las 08:05:41p. m. -0500, Greg Rivers via
freebsd-ports escribió:
> 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
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
14 matches
Mail list logo
