| 1 |
on 02/01/2012 11:21 PM Matthias Krebs wrote the following: |
| 2 |
> On 02/01/2012 10:05 AM, Thanasis wrote: |
| 3 |
>> Has anyone ever seen the following strange behaviour? |
| 4 |
>> While updating the system with emerge, after each installation of a |
| 5 |
>> package, before it starts emerging the next one, it pauses for a minute |
| 6 |
>> or two, then displays "alarm signal" (without the quotes) on a new line, |
| 7 |
>> and continues to emerging the next package. |
| 8 |
> Hi Thanasis, |
| 9 |
> |
| 10 |
> this message is from emerge /portage: |
| 11 |
> grep -r "alarm signal" /usr/lib64/portage/* |
| 12 |
> Binary file /usr/lib64/portage/pym/portage/exception.pyo matches |
| 13 |
> Binary file /usr/lib64/portage/pym/portage/exception.pyc matches |
| 14 |
> /usr/lib64/portage/pym/portage/exception.py: raise |
| 15 |
> AlarmSignal("alarm signal", |
| 16 |
> |
| 17 |
> This one matches your one minute: |
| 18 |
> /usr/lib64/portage/pym/portage/elog/mod_mail_summary.py: |
| 19 |
> AlarmSignal.register(60) |
| 20 |
> |
| 21 |
> Look like a timeout during mail sending to me. You have probably elog |
| 22 |
> mail sending configured in make.conf and your mailserver is borked. |
| 23 |
> |
| 24 |
|
| 25 |
You were right. I hadn't configured the /etc/mail/aliases file. |
| 26 |
Thanks ! |
Archives