A Dimarts 15 Maig 2012, Roland Gruber va escriure: > Hi Leo, > > On 13.05.2012 19:29, Leopold Palomo Avellaneda wrote: > > uhe only thing that I have found is this message in nslcd: > > > > May 13 01:04:08 orion nslcd[2534]: [d2daa8] nslcd_group_byname(+): > > invalid group name May 13 01:04:10 orion nslcd[2534]: [0bccf7] > > nslcd_passwd_byname(+): invalid user name > > I never saw this kind of messages. Could be related to this issue. > > Unfortunately, I am running out of ideas what causes this problem in > your environment.
Hi, I have found some info. Monitoring /var/log/auth , lamdaemon never contact to the server when a new quota is assigned. However, with the test, I can see the connection and the sudo execution. In the quota section, in the mount device field we have tested the real device (/dev/mapper/...) and the real mount point (not the bind used) Why lamdaemon is never called when a new quota is assigned? Regards, Leo -- -- Linux User 152692 Catalonia ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Lam-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lam-public
