Date: Tue, 21 Mar 2017 21:36:37 -0400 (EDT) From: "Igor R." <freebsd@str.komkon.org> To: Ernie Luzar <luzar722@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: command line history broken in 11.0 Message-ID: <alpine.BSF.2.20.1703212132440.12389@tissa.komkon.org> In-Reply-To: <58D1C382.9090306@gmail.com> References: <alpine.BSF.2.20.1703211310410.12389@tissa.komkon.org> <58D1925B.8050500@gmail.com> <alpine.BSF.2.20.1703211656530.12389@tissa.komkon.org> <58D1C382.9090306@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 21 Mar 2017, Ernie Luzar wrote: > Igor R. wrote: >> >> >> Ernie, >> >> You assertion about -o option sounds reasonable. >> I didn't think through if it is consistent with the changes made between >> the versions, and I didn't check the earlier history of changes (which >> would make your aliases+history working in 10.x) of the code. >> >> But the changes between 10.3 and 11.0 were indeed related to signal vs >> fork, which would be in the right ballpark with what the option -o does, >> according to the man pages. >> >> By the way, - I am still curious if sending halt or reboot into background >> would also do what you wanted. If you have a box you can experiment with, - >> would you mind doing that? >> >> snip >> > > I do have a dev box at this time. That is where I did the testing about this > problem. I just tried "reboot & ; exit" and it did indeed work. > Thank you for testing it. So, then, indeed the problem is in the stdout being held by "reboot", not letting "exit" to work. Igor
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1703212132440.12389>