Hi,

I am using Eset NOD32 as antivirus on my OES2 server.

The Program-Installer created a local user called "eset".
This user is not LUM enabled and don't needs to be. It's only used locally by the daemon.

In the messages log theres the line:
Jun 24 15:11:46 s60392aa kernel: Couldn't get FDN from LUM for uid=1000, rc=2
Jun 24 15:11:46 s60392aa kernel: Couldn't get FDN from LUM for uid=1000, rc=2
Jun 24 15:11:46 s60392aa kernel: Couldn't get FDN from LUM for uid=1000, rc=2
Jun 24 15:11:46 s60392aa kernel: Couldn't get FDN from LUM for uid=1000, rc=2

several times every second !!!!!
It stresses my ndsd a lot (about 70% CPU Usage...) !!!

uid 1000 is the "eset" user.

I read in another thread, that this happens also with McAfee Scanner

What's wrong with that? Can I exclude this "eset" user from trying a LUM check or something?

Thanks
Tobi