Bug#486826: multipathd: suspicious file descriptors

[Ferenc Wagner]

Bastian Blank <waldi at debian.org> writes:

> On Thu, Jun 19, 2008 at 01:03:08PM +0200, Guido Günther wrote:
>
>> On Wed, Jun 18, 2008 at 02:22:41PM +0200, Ferenc Wagner wrote:
>>>  * Shouldn't a daemon process always use /dev/null as stdin/stdout/stderr?
>>
>> multipathd uses /dev/console to output messages if necessary. See
>> daemonize in the code. I'm not seeing anything really wrong with this.
>
> /dev/console is routed somewhere. In case of emergency it should write
> to syslog with the appropriate severity to get the admin notified.

Hi Bastian,

It may not belong here, but I'd be interested in this.  How is
/dev/console routed anywhere?  Isn't that what's specified on the
kernel command line, eg. the active vc or a serial line?

>>> The sockets seem reasonable (based on /proc/net/unix), but how could I find out
>>> what the pipe is for?  /proc/*/fd reveals writers only.
>
> lsof and grep? Otherwise: strace.

As you may have probably noticed, dpkg seems guilty in this.
-- 
Thanks,
Feri.