Bug#255128: cdrom-detect: Bad handling of mount error

[Osamu Aoki <osamu@debian.org>]

On Sun, Jun 27, 2004 at 08:54:48AM +0200, Osamu Aoki wrote:
> I will put updated patch, iso-image example, syslog-commented, etc at
> 
>   http://people.debian.org/~osamu/pub/d-i/

Uploaded with gpg/md5sum files

> It works but I think following messages after Detecting CD needs to be
> understood before applying.
> 
> | Jun 26 19:34:27 (none) user.notice cdrom-detect: Detected CD with 'testing' distribution
> | Jun 26 19:34:27 (none) user.info main-menu[297]: (process:454): mount: Mounting /dev/cdroms/cdrom0 on /cdrom failed: Not a directory
> | Jun 26 19:34:27 (none) user.info main-menu[297]: (process:454): umount:
> | Jun 26 19:34:27 (none) user.info main-menu[297]: (process:454): /cdrom
> | Jun 26 19:34:27 (none) user.info main-menu[297]: (process:454): : Invalid argument

Let me claryfy my question.

Are messages in syslog listed exactly when the original error happened?

Are these redirected STDERR messages are stored until child process
"cdrom-detect" exits and returns control to "main-menu"?  

It looks like "main-menu" prints previously accumulated messages to
syslog when gaining control.  Then these are expected results.

Osamu