On Sat, Mar 19 2016, Michael Meskes <mes...@debian.org> wrote: > This is my second and last try. Could one of you please, pretty please, > describe the bug and explain what does not work although it should, ideally in > a way that makes it possible for me to reproduce it? So far, this bug report > has nothing to work with.
If you did ask before, I didn't receive anything. But anyway, it's easy. To get exactly the same behavior, on sid, login as root. Then: sudo -u user write user Where "user" is any username of a valid, logged-in account with messages enabled. Do you agree here, that write shouldn't prevent me to write to myself in this case? Pretty obvious. Where this behavior actually happens you ask? I want to notify myself when running in a cron job. Or at completion of scripts in batch scripts, or job schedulers, or anything that changes username for any reason whatsoever. If I didn't want messages, I would turn them off (which is the default anyway). Now, the bigger picture is that the check itself is bogus. Write shouldn't care about the original uid at all. What exactly is this check preventing? I hope this is clear now.
