I've also seen this while making ports. If I ^C while fetch is trying to
connect to the distfile site, it doesn't die. It might be that the mk.*
stuff is spinning off shells and allowing them to become disconnected from
terminal input somehow.
> -----Original Message-----
> From: Szilveszter Adam [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, June 14, 2001 2:12 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Clever! The kernel make that won't die...
>
>
> On Thu, Jun 14, 2001 at 12:38:43PM -0700, Matthew Jacob wrote:
> >
> > Heh- is this a bug or a feature?
> >
> > Making a kernel, no -j args, -current, tot
>
> tot... what?:-) Hello? Are you still there?:-)
>
> > ....oot/kernel make all
> > ===> 3dfx
> > ^C <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<^C'd it....
> >
> > nellie.feral.com > ===> accf_data
> > root mak===> accf_http
> > e
> > nellie.feral.com > ===> agp
> > ===> aha
> > fg===> amr
> >
> > bash: fg: current: no such job
> > nellie.feral.com > ===> an
>
> Well... this seems rather strange... is this several ttys
> output or just
> one?
>
> > That make- takes a licking, but keeps on ticking.....
>
> Yes, FreeBSD's real mascot is the Energizer Bunny don't you
> know? It just
> keeps going and going and going and ...
>
> Seriously: no, I have never seen anything like it. And I
> never use -j for
> kernel builds either... what is possible is however this:
> there was some
> talk about ^C, ^Z and friends being incorrectly masked by the
> login routine
> thus making these useless in some cases even after login. (With the
> original point being that you shouldn't be able to use these
> while logging
> in) This is supposed
> to be fixed now, but maybe you have the buggy version
> running? Also, the
> talk was that while bash (and sh?) were affected, tcsh
> wasn't, and since
> that's what I use, maybe that's why I never noticed this...
>
> What is the date of your current world?
>
> --
> Regards:
>
> Szilveszter ADAM
> Szeged University
> Szeged Hungary
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
