On Sun, 20 Aug 2006, Rod Dorman wrote:
> Well I'm still not clear on the issue.
>
> Is it that running postfix-enable changes /etc/mailer.conf? Thats an
> optional step, not part of the pkg_add.
The mailer.conf is forcibly replaced with mailer.conf.pre-postfix on
upgarde (or uninstall) - this
On Sun, 20 Aug 2006, Rod Dorman wrote:
Well I'm still not clear on the issue.
Well compare the mailer.conf files that are in the attached log
and see what command I ran. I had my mail server not functioning
for a day or so, because of this issue.
It'd also be nice to get rid of those warnings
On Sunday, August 20, 2006, 06:11:21, Morten Liebach wrote:
> On 2006-08-20 12:07:18 +0200, Morten Liebach wrote:
>> On 2006-08-20 10:20:08 +0300, Antti Harri wrote:
>>> is this normal behaviour? As far as I know ports should
>>> not touch files in /etc (excluding samples):
>>
>> They should, by d
On 2006-08-20 12:07:18 +0200, Morten Liebach wrote:
> On 2006-08-20 10:20:08 +0300, Antti Harri wrote:
> >
> > Hello,
> >
> > is this normal behaviour? As far as I know ports should
> > not touch files in /etc (excluding samples):
>
> They should, by defaults and design.
>
> FreeBSD (and perhap
On 2006-08-20 10:20:08 +0300, Antti Harri wrote:
>
> Hello,
>
> is this normal behaviour? As far as I know ports should
> not touch files in /etc (excluding samples):
They should, by defaults and design.
FreeBSD (and perhaps NetBSD) use another .../etc for their packages conf
files, but OpenBSD
Hello,
is this normal behaviour? As far as I know ports should
not touch files in /etc (excluding samples):
$ echo $PKG_PATH
ftp://openbsd.fi/openbsd/3.9/packages/i386/
$ sudo pkg_add postfix-2.2.8p1
postfix-2.2.8p1: complete
--- postfix-2.2.8p1 ---
-> Creating /etc/mailer.conf.
