Navigation

damir · #11 14th July 2010, 16:27

Quote:

Originally Posted by voltron81

So why it's in the how-to if at the end ispconfig is not using it?
Can I even remove it?

I'm not sure if it safe to remove it, but to stop it should be safe. I let Till or someone else answer if it's safe to remove it.

till · #12 14th July 2010, 16:33

Quote:

So why it's in the how-to if at the end ispconfig is not using it?
Can I even remove it?

If you would remove it then you would remove amavisd with it and if it would not be needed then it would not have been part of the perfect setup tutorial. So what I told you above is to stop it and not to remove it.

voltron81 · #13 14th July 2010, 16:45

Quote:

Originally Posted by till

If you would remove it then you would remove amavisd with it and if it would not be needed then it would not have been part of the perfect setup tutorial. So what I told you above is to stop it and not to remove it.

So Till you mean just kill the PID related with spamd?
Any idea why the free memory is jumping too much?
Could it be the cause of the crash of yesterday in one of the server? (they was online working perfectly for like 8 months)

Thanks
Michele

till · #14 14th July 2010, 16:47

Quote:

So Till you mean just kill the PID related with spamd?

No. On linux you stop software by using the start /stop script in /etc/init.d/

voltron81 · #15 14th July 2010, 17:41

ah ok so I'll use

Code:

 /etc/init.d/spamassassin stop

Let's see then if I've benefit on the RAM usage...
Thanks
Michele

voltron81 · #16 15th July 2010, 10:20

Hello,
unfortunately also without the spamd process, the usage of memory is jumping, in both servers, really a lot.
For example srv1 (4GB ram) is jumping from 1.8GB free to 30MB free... srv2 (1GB ram) is jumping from 500MB free to 20MB free...

Any suggestion?

Thanks
Michele

till · #17 15th July 2010, 10:21

Thats ok. The Linux kernel uses all free ram to cache harddisk requests. As long as your swap dont get filles 100%, then this is the normal and intended behaviour of the Linux kernel.

voltron81 · #18 15th July 2010, 10:32

Hi Till,
thanks for your answer.

I'm really happy to know that it's a normal behaviuor...

Anyway I still don't know how was possible the crash of srv1 2 days ago... it was something related with the segmentation fault... I've run a test of the RAM, but it was fine, so it was not an hardware fault...