1 |
On 15 Mar 2010, at 20:46, David W Noon wrote: |
2 |
>>> ... |
3 |
>>> Because emerge jobs produce copious amounts of output that is |
4 |
>>> difficult |
5 |
>>> to read as it scrolls past. I much prefer the cron daemon or at |
6 |
>>> daemon |
7 |
>>> to send me the output as email, so I can scroll backwards and |
8 |
>>> forwards through it at my leisure. |
9 |
>> |
10 |
>> `man screen` |
11 |
> |
12 |
> I don't have a man page for "screen". |
13 |
|
14 |
This is obviously because it isn't installed. |
15 |
|
16 |
I'm going to assume that you're not being facetious, however I'm |
17 |
amazed you don't know `screen`. Everyone should know `screen`! It's |
18 |
amazing, and I can't believe that if you had tried it then you |
19 |
wouldn't have it installed. I sure you'll wonder how you lived without |
20 |
it. |
21 |
|
22 |
You should try it: |
23 |
|
24 |
`emerge screen` (don't sync just yet) |
25 |
|
26 |
Now type: |
27 |
|
28 |
`screen sudo eix-sync` |
29 |
|
30 |
Wait for syncing to start, then press ctrl-a (together) then the d key. |
31 |
|
32 |
Close the terminal window you're working in, if you like. Open |
33 |
another. Or ssh in from another box. |
34 |
|
35 |
Type: |
36 |
|
37 |
`screen -Rd` |
38 |
|
39 |
You should see all the sync output scrolling past. So press ctrl-a |
40 |
followed by the escape key. Use ctrl-u to scroll up and see what you |
41 |
missed. ctrl-d scrolls down and hitting escape 2 or 3 times exits the |
42 |
"scrollback mode". |
43 |
|
44 |
I'm not saying that this is better than having syncs performed by cron |
45 |
job and the output emailed to you. In fact, that's something I've been |
46 |
meaning to get round to setting up here. If I had the output of |
47 |
(sync'd) `emerge -upv world` emailed to me weekly then it might ensure |
48 |
that my irregular habits don't cause me to overlook updates. |
49 |
|
50 |
HOWEVER, this branch of the thread has followed from your surprise |
51 |
that people might run emerge by hand, and your reasons for this (very |
52 |
first quoted above). I'm just saying there's nothing wrong with |
53 |
emerging or syncing by hand. You can easily scroll back and review any |
54 |
output that you need to - in fact the obvious way to do this is using |
55 |
a conventional GUI terminal emulator in a windowing environment. |
56 |
|
57 |
Also: grep PORTAGE_ELOG_MAIL /usr/share/portage/config/make.conf.example |
58 |
This ensures you see all the *important* output of portage, without |
59 |
having to watch the whole darn compiler output, which is pretty |
60 |
useless. You just get an email for every package upon which Portage |
61 |
has a comment to make. |
62 |
|
63 |
Other stuff you can do with `screen`: |
64 |
|
65 |
ctrl-a c - create a new screen "window" |
66 |
ctrl-a n - next screen "window" |
67 |
ctrl-a p - previous |
68 |
ctrl-a ? - help |
69 |
ctrl-a " - list open screen windows, select one |
70 |
ctrl-a A - name a screen window, see above (capital "A") |
71 |
|
72 |
Stroller. |