[gentoo-amd64] Interrupting portage gracefully

[gentoo-amd64] Interrupting portage gracefully

[Peter Humphrey]

Does anyone here know of a signal I can pass to portage to make it stop at 
the end of the current package? Quite often I find I'm emerging quite a lot 
of packages, and I'd like to shut the machine down for the night and resume 
in the morning. (I have been running it all night, but it's getting to be a 
bit noisy in the fan department.)

-- 
Rgds
Peter
-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: Interrupting portage gracefully

[Duncan]

Peter Humphrey <prh@gotadsl.co.uk> posted
200611231821.13640.prh@gotadsl.co.uk, excerpted below, on  Thu, 23 Nov
2006 18:21:13 +0000:

> Does anyone here know of a signal I can pass to portage to make it stop at 
> the end of the current package? Quite often I find I'm emerging quite a lot 
> of packages, and I'd like to shut the machine down for the night and resume 
> in the morning. (I have been running it all night, but it's getting to be a 
> bit noisy in the fan department.)

I don't believe there's a way to do it other than manually (watching for
the right moment and stopping it then), but using the --resume switch will
resume it at the same package, and if you use FEATURES=ccache and have it
setup correctly, the compile to the point of interruption will have been
cached so that package should merge faster, as well.  It'll still take
awhile as the configure steps repeat, and the linking and other
non-compile steps repeat as well, but the actual compilation should be
cached, so that part will be faster, on the package it's doing twice.

Of course, there are some I'd still not want to interrupt.  a gcc compile,
or glibc, come to mind, as does kdelibs if you have it merged, and from
what I read, openoffice, unless they are just barely started.  However, an
emerge --pretend or --ask can give you an idea of if and where they are in
the list, and you can schedule accordingly.

Alternatively, do a pretend, to get a list, and then emerge individual
packages.  I often do this with --tree, to get an idea of the
dependencies, and then do several merges in parallel (such that there
aren't any conflicting dependencies, thus the --tree), since portage
otherwise doesn't make very efficient use of multiple CPUs for much of the
emerge run.  The configure step for instance is generally single-job
serial, as are most of the other steps other than the actual compile. 
Even the compile is often forced to -j1 for individual packages due to job
ordering issues if -jX were allowed, so the /only/ way I've found to
efficiently make use of even TWO-way SMP is to invoke up to five emerges
in parallel.  The problem will be even worse once I upgrade to dual-core
Opteron 285s, thus four-way SMP (I see prices are down to $1200-ish for
the pair, now).

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Interrupting portage gracefully

[Christoph Mende]

[-- Attachment #1: Type: text/plain, Size: 490 bytes --]

On Thu, 2006-11-23 at 18:21 +0000, Peter Humphrey wrote:
> Does anyone here know of a signal I can pass to portage to make it stop at 
> the end of the current package? Quite often I find I'm emerging quite a lot 
> of packages, and I'd like to shut the machine down for the night and resume 
> in the morning. (I have been running it all night, but it's getting to be a 
> bit noisy in the fan department.)

You could ^C out of the current process and emerge --resume the next day

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 827 bytes --]

Re: [gentoo-amd64] Interrupting portage gracefully

[Thomas Rösner]

Christoph Mende wrote:
> On Thu, 2006-11-23 at 18:21 +0000, Peter Humphrey wrote:
>   
>> Does anyone here know of a signal I can pass to portage to make it stop at 
>> the end of the current package? 
>>     
>
> You could ^C out of the current process and emerge --resume the next day
>   

^Z and suspend-to-disk?

Regards,
    T.
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Interrupting portage gracefully

[Peter Davoust]

I don't know if this helps, but I usually run emerge <package> && init
0 so it shuts off after it's finished (it would be nice if portage had
an --shutdownafter option, but oh well). The only problem is that if
there's an error in portage it won't shut down. Other than that, try
replacing the fan. (Of course if you have a laptop, then that idea's
out the window).

-Peter

On 11/23/06, Thomas Rösner <Thomas.Roesner@digital-trauma.de> wrote:
> Christoph Mende wrote:
> > On Thu, 2006-11-23 at 18:21 +0000, Peter Humphrey wrote:
> >
> >> Does anyone here know of a signal I can pass to portage to make it stop at
> >> the end of the current package?
> >>
> >
> > You could ^C out of the current process and emerge --resume the next day
> >
>
> ^Z and suspend-to-disk?
>
> Regards,
>     T.
> --
> gentoo-amd64@gentoo.org mailing list
>
>

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Interrupting portage gracefully

[Michael Weyershäuser]

[-- Attachment #1: Type: text/plain, Size: 822 bytes --]

Peter Davoust wrote:
> I don't know if this helps, but I usually run emerge <package> && init
> 0 so it shuts off after it's finished (it would be nice if portage had
> an --shutdownafter option, but oh well). The only problem is that if
> there's an error in portage it won't shut down. 

Try "emerge foo; shutdown -h now" instead, that won't break if there is
an error during the emerge and will shut down the computer. Of yourse
you need to check if all packages really emerged the next day.

> On 11/23/06, Thomas Rösner <Thomas.Roesner@digital-trauma.de> wrote:
>>
>> ^Z and suspend-to-disk?
>>

No need for ^Z, suspend should be able to handle suspending during a
running emerge and resume at the same point when coming back up. I've
done this several times with suspend2 and it works just fine.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

Re: [gentoo-amd64] Interrupting portage gracefully

[Kevin F. Quinn]

[-- Attachment #1: Type: text/plain, Size: 1050 bytes --]

On Thu, 23 Nov 2006 16:54:53 -0800
"Peter Davoust" <worldgnat@gmail.com> wrote:

> I don't know if this helps, but I usually run emerge <package> && init
> 0 so it shuts off after it's finished (it would be nice if portage had
> an --shutdownafter option, but oh well). The only problem is that if
> there's an error in portage it won't shut down.

That's because by using '&&', you are explicitly telling bash to run
the second command only if the first command succeeds.  To run the
second command regardless, use ';' to separate the commands:

emerge <package> ; init 0

It's a good idea to have logging switched on so if stuff failed you can
find out why later.  In make.conf set PORT_LOGDIR to a directory that
exists; also setup the elog stuff, PORTAGE_ELOG_* -
see /etc/make.conf.example (which is the only place they're documented)
- I use:

PORTAGE_ELOG_CLASSES="info warn error log"
PORTAGE_ELOG_SYSTEM="save"

which just dumps the relevant bits into a subdirectory "elog" of
${PORT_LOGDIR}.

-- 
Kevin F. Quinn

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-amd64] Interrupting portage gracefully

[Rob Lesslie]

Suspend to ram or to disk

-- 
Rob Lesslie
-- 
gentoo-amd64@gentoo.org mailing list