Re: hostname in aliases.db

2017-08-06 Thread Marat Khalili
On 05/08/17 21:30, /dev/rob0 wrote: On Sat, Aug 05, 2017 at 07:58:19PM +0300, Marat Khalili wrote: That's what I'd like to know to, is this hostname mention even being used? I doubt it is, but I am too lazy / busy to test. :) You could also consult your Berkeley DB documentation. I do know th

Re: hostname in aliases.db

2017-08-05 Thread /dev/rob0
On Sat, Aug 05, 2017 at 07:58:19PM +0300, Marat Khalili wrote: > > See also postalias(1), but I'm still not sure that this is a > > real problem. Does something in the container not work > > properly with host-generated aliases.db? > > That's what I'd like to know to, is this hostname mention even

Re: hostname in aliases.db

2017-08-05 Thread Marat Khalili
You might indeed want to generate your aliases.db for each container, and chroot(1) might be a means to do that. Completely forgot about chroot, much better than starting whole container. See also postalias(1), but I'm still not sure that this is a real problem. Does something in the containe

Re: hostname in aliases.db

2017-08-05 Thread /dev/rob0
On Sat, Aug 05, 2017 at 07:11:08PM +0300, Marat Khalili wrote: > I'm cloning an LXC container which optionally can contain postfix > installation. After cloning the filesystem there's a number of > places I need to change the hostname in. > > I used grep to search for these places and unexpected

hostname in aliases.db

2017-08-05 Thread Marat Khalili
I've got the following problem which is not critical but still interesting. I'm cloning an LXC container which optionally can contain postfix installation. After cloning the filesystem there's a number of places I need to change the hostname in. I used grep to search for these places and unexp