Re: **IMPORTANT** Slink sendmail and libdb2
Sendmail slowly is moving everything to /etc/mail - but they haven't hit
all the databases yet.
I can update the features for Debian, and move the default files from
/etc/ to /etc/mail/
Without parsing /etc/mail/sendmail.mc, I can't tell what type of
encoding is used for the databases, so I don't think I can do the
makemaps automagically ;-{
--
Rick Nelson
On 28 Oct 1998, John Goerzen wrote:
> Date: 28 Oct 1998 13:02:19 -0600
> From: John Goerzen <jgoerzen@complete.org>
> To: Remco van de Meent <remco@debian.org>
> Cc: debian-user@lists.debian.org
> Subject: Re: **IMPORTANT** Slink sendmail and libdb2
> Resent-Date: 28 Oct 1998 19:02:26 -0000
> Resent-From: debian-user@lists.debian.org
> Resent-cc: recipient list not shown: ;
>
> Remco van de Meent <remco@debian.org> writes:
>
> > On Tue, Oct 27, 1998 at 08:35:35AM -0600, John Goerzen wrote:
> >
> > : Would it be possible for the sendmailconfig to update these databases?
> > : It wouldn't be that hard, I think. Also, how about updating the defailts
> > : so that they are stored in /etc/mail instead of /etc?
> >
> > They default to /etc/mail, except for aliases.db, which should be in /etc
> > (Debian Policy, 4.5).
>
> I know what policy says, but this is not how it works. mailertable,
> etc. are in /etc and not /etc/mail.
>
> > Because of the different db-structures you can use (hash, btree, etc.), I'd
> > say don't let an automatic install program update those databases. It should
> > even be able to process customized sendmail.cf's in order to work without
> > failure. I personally wouldn't want any program changing those databases
> > itself...
>
> It's a pain to manually have to run a long makemap command each time
> something is updated. There has GOT to be a better way...
>
>
>
>
Reply to: