This is normal unix behavior (unless you have some kind of shell that I'm unfamiliar with.)
When you use & to create a subjob, it is still attached to your terminal session. Take a look at the at(1) or batch(1) commands if you really want to execute a command and logout while it's still running. -----Original Message----- >From: Dominique Dhumieres <domi...@lps.ens.fr> >Sent: Apr 16, 2010 2:10 PM >To: gcc@gcc.gnu.org >Subject: Question about perl while bootstrapping gcc > >Hi! > >I use to build gcc with a command line such as > >make -j2 >& somelogfile & > >I recently found that if I logout, the build fails with > >perl: no user 501 > >Is this a bug or a feature? In the former case I'll open a PR. >In the later is it documented somewhere that you should not logout >while building gcc? If yes, is it possible to have a pointer? > >TIA > >Dominique