On 30-Aug-2000 Dan Horth spoke something to the effect:
> since upgrading to latest linuxconf and regenerating my
> /etc/sendmail.cf from it I get this message:
>
> Warning: .cf file is out of date: sendmail 8.9.3 supports version 8,
> .cf file is version 7
>
> when using mail from the shell - any pointers as to why linuxconf is
> generating a v7 config file all of a sudden?
Because linuxconf (despite the brave efforts of everyone involve) is buggy,
for mail and bind particularly. To date, it has _never_ successfully
created an updated sendmail.cf for me. I try it ocassionally to see if it
has been repaired. I've never had success. Thank god I learned to keep
backs on UNMOUNTED partitions (it has mangled other, non-standard
directories on me, too).
I think if linuxconf is going to insist on being the config tool for
everything, it should perform its actions the way the other deveoplers
intended. In the case of sendmail, that means not editting sendmail.cf
directly. Rather it should go through the whole M4 method that is intended
to create such files and let the proper rules for the version installed be
created. Currently, it handles direct edits and uses either outdated
versions or versions newer than one has installed in most cases.
I also think linuxconf development should remove all of the extremely buggy
configuration items, get them tested and fixed as well as they can (with
beta versions only and lots of warnings), then release versions with the
bugs removed (as much as possible). The problem appears that several items
don't work well and all get fixed as problems arise. That leaves things
wide open to *.cf versions for version 7 being generated for users with
version 8 or older versions or whatever installed.
--
Failure is not an option. It comes bundled with every Microsoft product.
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
