V2 shibd daemon should not fprintf to stderr in normal circumstances

Description

(previous report was on 1.3, this is on 2.0 beta)

As a polite daemon, the shibd application shouldn't write stuff to its stderr if nothing bad has happened. As it is, it says the following on startup:

loading configuration file: /etc/shibboleth/shibboleth2.xml

This comes from line 135 in shibd.cpp:

fprintf(stderr, "loading configuration file: %s\n", shar_config);

Environment

None

Activity

Scott Cantor
September 21, 2007 at 10:14 AM

Fixed in svn.

Fixed

Details

Assignee

Reporter

Components

Affects versions

Created September 21, 2007 at 8:21 AM
Updated September 21, 2007 at 10:14 AM
Resolved September 21, 2007 at 10:14 AM