Bug #52
closed
newaliases not run after install
Added by bsd_usr almost 19 years ago.
Updated over 15 years ago.
Description
Greetings,
I wanted to make note that newaliases doesn't seem to be run after
installation.
How did I find this bug? Well, I installed DragonFlyBSD 1.4 (overwriting
DragonFlyBSD Preview) yesterday because I wanted to do a nice clean
installation. I came to work this morning and found this in my logs:
Jan 10 03:02:25 www sm-mta74783: k0AB2PmO074783: SYSERR: hash
map "Alias0": missing map file /etc/mail/aliases.db: No such file or
directory
Jan 10 03:02:25 www sm-mta74787: k0AB2PDj074787: SYSERR: hash
map "Alias0": missing map file /etc/mail/aliases.db: No such file or
directory
Jan 10 03:02:25 www sm-mta74789: k0AB2PmO074783: SYSERR: hash
map "Alias0": missing map file /etc/mail/aliases.db: No such file or
directory
Jan 10 03:02:25 www sm-mta74791: k0AB2PDj074787: SYSERR: hash
map "Alias0": missing map file /etc/mail/aliases.db: No such file or
directory
It's not a huge deal. After running newalises, everything seemed fine
although it seems like that's something that should be done
automatically upon installation.
Thanks,
Joseph Garcia
:
:
:Greetings,
:
:I wanted to make note that newaliases doesn't seem to be run after
:installation.
:
:How did I find this bug? Well, I installed DragonFlyBSD 1.4 (overwriting
:DragonFlyBSD Preview) yesterday because I wanted to do a nice clean
:installation. I came to work this morning and found this in my logs:
:
:Jan 10 03:02:25 www sm-mta74783: k0AB2PmO074783: SYSERR: hash
:map "Alias0": missing map file /etc/mail/aliases.db: No such file or
:directory
:Jan 10 03:02:25 www sm-mta74787: k0AB2PDj074787: SYSERR: hash
:map "Alias0": missing map file /etc/mail/aliases.db: No such file or
:directory
:Jan 10 03:02:25 www sm-mta74789: k0AB2PmO074783: SYSERR: hash
:map "Alias0": missing map file /etc/mail/aliases.db: No such file or
:directory
:Jan 10 03:02:25 www sm-mta74791: k0AB2PDj074787: SYSERR: hash
:map "Alias0": missing map file /etc/mail/aliases.db: No such file or
:directory
:
:It's not a huge deal. After running newalises, everything seemed fine
:although it seems like that's something that should be done
:automatically upon installation.
:
:Thanks,
:
:Joseph Garcia
Yup, it should have and didn't. I'll add it to the errata.
-Matt
Matthew Dillon
<dillon@backplane.com>
Matthew Dillon wrote:
Yup, it should have and didn't. I'll add it to the errata.
-Matt
Matthew Dillon
<dillon@backplane.com>
I have a feeling that this occured in 1.2 as well. It's just a feeling.
It's been a long while since I installed 1.2 and there's no reason to go
back anyway, but I think it could be an old bug or something. Just
thought I'd let you know.
Joseph Garcia
:
:Matthew Dillon wrote:
:
:>
:> Yup, it should have and didn't. I'll add it to the errata.
:>
:> -Matt
:> Matthew Dillon
:> <dillon@backplane.com>
:
:I have a feeling that this occured in 1.2 as well. It's just a feeling.
:It's been a long while since I installed 1.2 and there's no reason to go
:back anyway, but I think it could be an old bug or something. Just
:thought I'd let you know.
:
:Joseph Garcia
Yah. its one of those bugs that I think a lot of people noticed,
but then just did 'newalias' and forgot about it.
-Matt
Matthew Dillon
<dillon@backplane.com>
As I've doing some new DF fresh install on my test machine, I've installed
1.12.0 and 1.12.2 recently and I have not encountered this problem with aliases.
bug reappeared. we need to run newaliases when populating ${DESTDIR}/etc, I
believe.
Fixed by 03e2a3c5ec51df1be822987bcc021bccfbd23801
Also available in: Atom
PDF