vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| When I want to emerge hal, everything goes fine, I reach "merging ..." but then my system freezes after a few minutes. It seems that the biggest CPU load is syslog-ng during this phase (top). I've tried a lot of things, I'm out of ideas ! SOS ! |
| |||
| Albert said something like a ... > I've tried a lot of things, I'm > out of ideas ! SOS ! Without much in the way of info from you... do it without X. Consider a new --sync, then re-try your merge. Look at the logs in /var/log/dmesg, /var/log/emerge. log/var/log/everything. -- BlackTopBum You don't skateboard? What worthwhile thing are you doing !? |
| |||
| BlackTopBum has offered us the following clue : > Albert said something like a ... > > >> I've tried a lot of things, I'm >> out of ideas ! SOS ! > > Without much in the way of info from you... do it without X. Consider a > new --sync, then re-try your merge. > > Look at the logs in /var/log/dmesg, /var/log/emerge. > log/var/log/everything. Thank you for the advice. What happened was quite strange, it's the first time I see such a problem. The merging procedure was trying unsuccessfully to put haldaemon in the cdrw group and was filling the "messages" log in a crazy loop. That was the reason why syslog was high on cpu load. I've put haldaemon in the group manually and now it is OK. The curious thing is that the merging process then registered many new entries in /etc/group without any problem. |