Date: Sun, 16 Jul 2017 11:07:52 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 220759] jail -i / -q is not acting as described Message-ID: <bug-220759-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220759 Bug ID: 220759 Summary: jail -i / -q is not acting as described Product: Base System Version: 11.0-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: heinz@project-fifo.net The manual for jail read: -i Output (only) the jail identifier of the newly created jail(s). This implies the -q option -q Suppress the message printed whenever a jail is created, modified or removed. Only error messages will be printed. however, this does not reflect how jail behaves. In addition to error messages, it also prints all output from, for example, 'exec.start'. This can lead to the output of jail being rather odd, and hard/impossible? to parse and it seems in conflict with 'Only error messages will be printed.' as the output from 'exec.start' is not an error. That all said I can see why this happens, I suspect the output of exec.start is not considered to be output from the jail command. It is however pointed to the same FD (stdout) so I think for all intents and purposes, as anyone calling jail the output comes from jails. This bug can simply be reproduced by creating a new jail using the -i option and adding exec.start="echo hello". -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-220759-8>