No problem, i probably just hit reply blindly the last time.
On the issue:
On my laptop is a bit different story:
lsof | grep jitsi | grep home came up empty.
lsof | grep java | grep home:
$ lsof | grep java | grep home
java 11937 laca mem REG 8,1 9432 955724 /home/laca/.fontconfig/4f728d7f57188d314fd5d410f0669674-le32d4.cache-3
java 11937 laca 1w REG 8,1 851453666 889450 /home/laca/.xsession-errors (deleted)
java 11937 laca 2w REG 8,1 851453666 889450 /home/laca/.xsession-errors (deleted)
java 11937 laca 13r REG 8,1 0 1052884 /home/laca/.sip-communicator/sip-communicator.bin/cache.lock
java 11937 laca 123w REG 8,1 0 1068970 /home/laca/.sip-communicator/log/sip-communicator0.log.0.lck
java 11937 laca 124w REG 8,1 21813 1069058 /home/laca/.sip-communicator/log/sip-communicator0.log.0
I deleted the .xsession-errors file at some point because it grew too large.
Anyway "tail -f /home/laca/.sip-communicator/log/sip-communicator0.log.0" showed little activity (only on login/logout a few lines).
Looking at these shows no indication of any suspicious activity.
After a while i found the culprit - it is laptop-mode set to write to disk every 2 seconds when on battery. When i changed that, the writes occured exactly at the specified period.
Thanks for the assistance anyway. My bad.
On Fri, 09 Sep 2011 11:26:17 +0300, Emil Ivov <email@example.com> wrote:
I just noticed we've gone private at some point. Would you mind
replaying this discussion on the dev list? I can also forward your mails
there if you prefer.
На 09.09.11 07:58, Kertesz Laszlo написа:
The output of
"lsof | grep Jitsi | grep home" is
java 17518 laca 12w REG 8,1 0 2228233
java 17518 laca 122w REG 8,1 0 2228659
java 17518 laca 123w REG 8,1 23452 2228238
The rest of the open files are in /usr/lib and there is no write access
On Thu, 08 Sep 2011 14:58:12 +0300, Emil Ivov <firstname.lastname@example.org> wrote:
Do you have a way of determining which files it is writing to?
What command are you using to make these stats?
На 03.09.11 06:15, Kertesz Laszlo написа:
It seems that Jitsi still writes to disk every second. I looked at iotop
and it has its process writing every second (11.5 KB/s). And i actually
hear the hard drive clicking and see the hdd activity led blinking when
does so it is real write. No other messenger that i know of does this
of ativity, It is annoying especially on laptops because it prevents te
drive standby leading to reduced battery life. I did have this issue in
some previous builds, for a time it seemed to go away though.
I have logging disabled from the menu.
Is this drive activity really necessary for jitsi to function?
I use Jitsi on Debian 32-bit with Java 1.6.26.
O zi buna,
Using Opera's revolutionary email client: http://www.opera.com/mail/