Thanks for the answer Viktor.
As I mentioned, mine was an attempt to parse/validate the syntax
externally, so I used the documentation as a guideline and probed with
postmap to see what it would actually accept or not.
I hope you will forgive me if I disagree on a specific case where I believe
th
On Sun, Jul 28, 2019 at 12:05:33AM +0300, Mantas Mikulėnas wrote:
> On Sat, Jul 27, 2019, 22:35 Wietse Venema wrote:
> >
> > Mantas Mikul?nas:
> > > Disregard this; I'm sure I have found the nss module that causes high
> > > memory usage.
> >
> > Which nss module would that be?
>
> It was libnss
On Sat, Jul 27, 2019 at 03:13:01PM +0200, Fulvio Scapin wrote:
> But, as I mentioned at the beginning, the inline table is the one leaving
> me slightly confused.
The syntax is *simple* (minimal features, which is not always the
same as: intuitive or "easy to use", but generally not too far off
t
On Sat, Jul 27, 2019, 22:35 Wietse Venema wrote:
>
> Mantas Mikul?nas:
> > Disregard this; I'm sure I have found the nss module that causes high
> > memory usage.
>
> Which nss module would that be?
It was libnss_myhostname (specifically the version that is included
with systemd).
Besides handli
Fulvio Scapin:
> Hello to everyone.
>
> I've been trying to write a small parser to parse Postfix lookup table
> calls for a piece of code I am developing.
>
> I have taken a look at the source code and then resorted to postmap -q
> invocations to empirically test the descriptions at
> http://www
Mantas Mikul?nas:
> Disregard this; I'm sure I have found the nss module that causes high
> memory usage.
Which nss module would that be? Postfix does not care how many routes
a system has, but it does care about local network interface addresses
and netmasks if main.cf:mynetworks does not specify
Disregard this; I'm sure I have found the nss module that causes high
memory usage.
--
Mantas Mikulėnas
Hello,
I have a hobby server that does a little bit of everything, including
1) receiving email via Postfix as a backup MX,
2) receiving ~70k IPv6 routes via BGP.
The problem I'm having is that when all ~70k routes are loaded into
the kernel (Linux), this somehow causes high memory usage in Postf
Hello to everyone.
I've been trying to write a small parser to parse Postfix lookup table
calls for a piece of code I am developing.
I have taken a look at the source code and then resorted to postmap -q
invocations to empirically test the descriptions at
http://www.postfix.org/DATABASE_README.ht
