Date: Mon, 3 Sep 2001 07:44:38 +0200 From: Andre Albsmeier <andre.albsmeier@mchp.siemens.de> To: jon@FreeBSD.org Cc: andre.albsmeier@mchp.siemens.de, freebsd-bugs@FreeBSD.org, cracauer@FreeBSD.org Subject: Re: bin/24591: jobs command differs in interactive vs. non-interactive /bin/sh Message-ID: <20010903074438.A40750@curry.mchp.siemens.de> In-Reply-To: <200109022320.f82NK9G13771@freefall.freebsd.org>; from jon@FreeBSD.org on Sun, Sep 02, 2001 at 04:20:09PM -0700 References: <200109022320.f82NK9G13771@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[ CC'ing Martin Cracauer...] On Sun, 02-Sep-2001 at 16:20:09 -0700, jon@FreeBSD.org wrote: > Synopsis: jobs command differs in interactive vs. non-interactive /bin/sh > > State-Changed-From-To: open->closed > State-Changed-By: jon > State-Changed-When: Sun Sep 2 16:16:45 PDT 2001 > State-Changed-Why: > If you want a shell that behaves the same way as an interactive shell, > start sh with the -i flag. Thanks for the explanation. > > The reason this does not work in non-interactive mode is because the command > string is not stored unless the shell is an interactive root shell. > See jobs.c line 678: > if (iflag && rootshell && n) > ps->cmd = commandtext(n); > Hmm, so I have to ask myself why it needs the iflag to store the commandtext... -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010903074438.A40750>