On 9 August 2015 at 18:19, Santiago Vila <sanv...@unex.es> wrote: > On Sun, Aug 09, 2015 at 07:14:30PM +0200, Reuti wrote: >> The profile is usually sourced. How does the error show up at the login >> prompt on Debian? > > The problem only happens in Debian testing and unstable, which I am not using > yet. > This is the original report which I received against base-files: > > https://bugs.debian.org/794727
Please notice the mesg(1) exit behavior is defined in POSIX http://pubs.opengroup.org/onlinepubs/9699919799/utilities/mesg.html Unfortunately the standard does not appear to be explicit whether the exit value should be set only when requesting write permissions (running without arguments), or if also when setting the permissions. IMHO the reasonable thing to do is to leave the return codes as they are to avoid breakage in existing usage. If someone needs messaging setting not to report exit codes then this functionality is safest to introduce with new option, such as --no-exit-code-status -- Sami Kerola http://www.iki.fi/kerolasa/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
