| View previous topic :: View next topic |
| Author |
Message |
scottneh
Apprentice
Joined: 07 Aug 2009
Posts: 239
Location: Where the Sewer meets the Sea
|
 Posted: Sun Sep 20, 2009 2:17 pm Post subject: Running Multiple emerges |
 |
|
| Anyone have any opinions on running multiple emerges in sepaerate terminal windows at the same time? Just curious ifits a good or bad practice? |
|
| Back to top |
|
 |
Hu
Moderator
Joined: 06 Mar 2007
Posts: 21619
|
| Posted: Sun Sep 20, 2009 3:35 pm Post subject: |
|
|
| It mostly works, but I would not recommend it for non-trivial cases. I had a bad experience with it once a few years ago when the locking made a mistake and allowed emerge #2 to start work on a package that emerge #1 was already building. If you are merging multiple packages that do not parallelize well, consider using the --jobs option to emerge, which will let it manage multiple merges in parallel. The problem I had was that two completely separate emerge processes were running, and thus were unaware of the details of each others' activities. If one instance of emerge manages all the jobs, it should avoid that problem. |
|
| Back to top |
|
|
saboya
Guru
Joined: 28 Nov 2006
Posts: 552
Location: Brazil
|
| Posted: Sun Sep 20, 2009 4:28 pm Post subject: |
|
|
| Basically what Hu said. If you emerge packages that don't depende on each other, you should be fine. |
|
| Back to top |
|
|
andreas_st
Tux's lil' helper
Joined: 26 Dec 2007
Posts: 112
Location: 48N 16E
|
| Posted: Sun Sep 20, 2009 5:53 pm Post subject: |
|
|
It is certainly not good practice. Things like | Code: | | emerge --resume --skipfirst |
may not work as expected when multiple emerge processes are active.
If you want to do more in parallel, edit /etc/make.conf and increase the number for -j in MAKEOPTS.
_________________
Registered Linux user #62727 |
|
| Back to top |
|
|
|
Portage & Programming
