On Fri, Oct 10, 2008 at 01:07:43PM +0200, Laszlo Nagy wrote:
>
>> Firstly, I see a periodic(8) job that DOES use find -sx, which means
>> your attempt to track it down was faulty, and your syntax should have
>> been "find -sx /" not "find / -sx". See here:
>>
>> /etc/periodic/security/100.chksetui
Firstly, I see a periodic(8) job that DOES use find -sx, which means
your attempt to track it down was faulty, and your syntax should have
been "find -sx /" not "find / -sx". See here:
/etc/periodic/security/100.chksetuid: find -sx $MP /dev/null -type f \
Thanks for clearing that out. :-)
On Fri, Oct 10, 2008 at 11:43:39AM +0200, Laszlo Nagy wrote:
>
If find / -sx is running and is consuming all CPU, what is the
value of vfs.ufs.dirhash_mem:
# sysctl -a | grep dirhash
>>> shopzeus# sysctl -a | grep dirhash
>>> vfs.ufs.dirhash_docheck: 0
>>> vfs.uf
Thank you very much! Probably you are right. Our users use shared IMAP
folders and sometimes they keep ten thousands of messages in one
folder. I have increased dirhash_maxmem to 64MB and see what happens.
Unfortunately, I cannot play with the hardware because it is in a
server park, and
If find / -sx is running and is consuming all CPU, what is the value of
vfs.ufs.dirhash_mem:
# sysctl -a | grep dirhash
shopzeus# sysctl -a | grep dirhash
vfs.ufs.dirhash_docheck: 0
vfs.ufs.dirhash_mem: 2095818
vfs.ufs.dirhash_maxmem: 2097152
vfs.ufs.dirhash_minsize: 2560
Ma
>Johan Hendriks írta:
>> If find / -sx is running and is consuming all CPU, what is the value of
>> >vfs.ufs.dirhash_mem:
>>
>> # sysctl -a | grep dirhash
>>
>shopzeus# sysctl -a | grep dirhash
>vfs.ufs.dirhash_docheck: 0
>vfs.ufs.dirhash_mem: 2095818
>vfs.ufs.dirhash_maxmem: 2097152
>vfs.uf
On Fri, Oct 10, 2008 at 11:13:00AM +0200, Laszlo Nagy wrote:
> Johan Hendriks írta:
>> If find / -sx is running and is consuming all CPU, what is the value of
>> vfs.ufs.dirhash_mem:
>>
>> # sysctl -a | grep dirhash
>>
> shopzeus# sysctl -a | grep dirhash
> vfs.ufs.dirhash_docheck: 0
> vfs.ufs
Johan Hendriks írta:
If find / -sx is running and is consuming all CPU, what is the value of vfs.ufs.dirhash_mem:
# sysctl -a | grep dirhash
shopzeus# sysctl -a | grep dirhash
vfs.ufs.dirhash_docheck: 0
vfs.ufs.dirhash_mem: 2095818
vfs.ufs.dirhash_maxmem: 2097152
vfs.ufs.dirhash_minsize: 25
This could be a periodic job (since you said this happens daily) which
runs early in the morning (2-3am?) and for some reason isn't finishing
in a timely manner. You haven't provided any actual ps -auxwww
data, so we can't easily discern if it's a periodic job or something
amiss on your sys
If find / -sx is running and is consuming all CPU, what is the value of
vfs.ufs.dirhash_mem:
# sysctl -a | grep dirhash
Make sure vfs.ufs.dirhash_mem: is not close to vfs.ufs.dirhash_maxmem:
Regards,
Johan Hendriks
Double -L Automatisering
No virus found in this outgoing message.
Checked by A
On Fri, Oct 10, 2008 at 10:40:01AM +0200, Laszlo Nagy wrote:
> Hi,
>
> A computer hangs every day in the morning at a specific time, between 8
> AM and 9 AM. We can ping it. Apparently the console works, also gdm
> works on it, but we are not able to login at all. ssh accepts
> connections,
Hi,
A computer hangs every day in the morning at a specific time, between 8
AM and 9 AM. We can ping it. Apparently the console works, also gdm
works on it, but we are not able to login at all. ssh accepts
connections, but the authentication does not continue (e.g. ssh client
waits for the s
12 matches
Mail list logo