lsb calls to usplash_write should fail silently

[Dustin Kirkland ]

Binary package hint: lsb

Init scripts, as well as other LSB-using scripts can be executed by non-privileged user. In such cases, the non-privileged user trying to execute usplash_write will yield an error message like:
  open: Permission denied

For example, in Intrepid, as a non-root user, run:
# /etc/init.d/ssh status
open: Permission denied
 * sshd is running.

This can be noisy and distracting, and in almost all cases, this is not a useful error message to that user.

:-Dustin

[Dustin Kirkland  (kirkland)]

Patch attached.

Colin previously suggested that this could be handled in usplash itself. I have that patch as well, but I would thing that this approach (patching callers of usplash_write) would be preferred.

Please review, and advise.

:-Dustin

[Dustin Kirkland  (kirkland)]

As Colin pointed out in IRC, the above patch will silence all errors thrown by usplash.

As a different approach, here is a simple patch to usplash_write that silences EACCES errors.

:-Dustin

[Dustin Kirkland  (kirkland)]

A bzr branch with these changes, proposed for merging:
 * https://code.launchpad.net/~kirkland/usplash/usplash.251656

:-Dustin

[Launchpad Janitor (janitor)]

This bug was fixed in the package usplash - 0.5.23

---------------
usplash (0.5.23) intrepid; urgency=low

  * usplash_write.c: do not perror(open) if EACCESS (LP: #251656).

 -- Dustin Kirkland <email address hidden> Mon, 28 Jul 2008 09:50:22 -0500