"Rolf Sommerhalder" <[EMAIL PROTECTED]> wrote:
> This simple configuration file for hoststated below is syntactically
> correct (and semantically, too), however apparently only if its file
> mode bits are 600 (which makes sense).
>
> Somehow, I ended up with mode bits being set to 644, upon which
> hoststated refused to accept it but throws an "Undefined error: 0".
> It took me a while to figure out that it occurs due to mode bits being
> set somewhat too liberal because the error does not provide any hint.
> Also, I only upgraded to -current last night, and the same
> configuration file was accepted with mode bits 644 by the latest
> available snapshot without complaint before upgrading.
>
> Actually, I just tried 'hoststated -d -f /etc/hoststated.rs' which
> throuws the same error, but only after hinting about the mode bits
> being wrong. So it might be helpful to just add the same hint output
> to the -n option as well.
>
> I had no opportunity to crosscheck on sparc64 -current yet, or to
> propose a small diff, sorry for that.
>
> Thanks,
> Rolf
>
There was indeed no provision to check for this when running hoststated
with -n. This will be fixed in CVS shortly.
