did you miss the file:read_file_info() in the handle_info() method?

Begin forwarded message:

From: Claes Wikstrom <klacke@tail-f.com>
Date: October 1, 2007 2:09:24 PM EDT
To: Richard <richard@bucker.net>
Cc: erlyaws-list@lists.sourceforge.net
Subject: Re: [Erlyaws-list] yaws guard expression

Richard wrote:

PS: I think the code must always continue.... the first error message should be an error message pertaining to this err. 

Yes, not enough badness to bail out. I changed the
error_logger message for this particular case. It still deserves
an entry in the error_log, since if/when it happens it means that
the local system is configured to auto purge logfiles in a way
yaws doesn't like.

Getting yaws to play nice with the normal way of rotating
logs, is an other story. Should/could be done, where by normal I mean
that at HUP/reload, all logfiles are simply reopened. That way a rotator can
rename files according to an external scheme and then HUP/reload yaws.
This is not how it works today though.