>Number:         13838
>Category:       bin
>Synopsis:       syslogd gives misleading error message when given bad argument to -p option
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Aug 31 16:07:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Ed Ravin
>Release:        1.5.1
>Organization:
Panix
>Environment:
NetBSD alexandria.nyc.access.net 1.5 NetBSD 1.5 (PANIX-RAID) #0: Fri Dec  1 22:42:53 EST 2000     marcotte@trinity.panix.com:/devel/netbsd/1.5/src/sys/arch/i386/compile/PANIX-RAID i386

>Description:
When syslogd is invoked with "-p filename" and the filename has a bad component in its path, (i.e. non existent directory), syslogd issues a misleading error message to the console:

   syslogd: can: No such file or directory

and then exits.

>How-To-Repeat:

syslogd -p /junk/bunk/wunk/thunk

  or, if you're not on the console:

syslogd -d -p /blunk/grunk/nunk/hunk
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted: