meta user
network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year, 9 months |
| seen | May 17 at 23:14 | |
| stats | profile views | 97 |
|
May 8 |
comment |
Wait for a X window to appear/disappear (in a sane way) Yes, I shouldn't really worry about this one anymore, you're right again. But I think I'll also loose this night of sleep compiling the kernel, since I want to check everything that might be waking constantly the disk, not only this particular Google Earth hack :) |
|
May 7 |
revised |
Wait for a X window to appear/disappear (in a sane way) backslashes were missing |
|
May 7 |
suggested | suggested edit on Wait for a X window to appear/disappear (in a sane way) |
|
May 7 |
comment |
Wait for a X window to appear/disappear (in a sane way) I believe there are times when reading a file, at least for the first time, will wake the disk too, isn't it? I'm wondering if blktrace would be the right tool for that, but it would require a kernel compilation # CONFIG_BLK_DEV_IO_TRACE is not set :( That is beyond the scope of this question, though. Thank you! |
|
May 7 |
accepted | Wait for a X window to appear/disappear (in a sane way) |
|
May 7 |
comment |
Wait for a X window to appear/disappear (in a sane way) Yes, exactly, -sync was supposed to do what I want, but it needs the while because it will eventually crash before the window appears, and wastes too much CPU. I actually compiled xdotool from source because the one from Debian was incredibly slow to type. Writing an application that interacts directly with X is actually beyond me. Thanks, though! |
|
May 7 |
revised |
Wait for a X window to appear/disappear (in a sane way) added 1 characters in body |
|
May 7 |
comment |
Wait for a X window to appear/disappear (in a sane way) @HaukeLaging could you explain a bit more about what I should try to achieve through a chroot to a ramdisk? |
|
May 7 |
comment |
Wait for a X window to appear/disappear (in a sane way) @msw I'm trying to fix the unfixable, which is an autosave feature for Google Earth (closed sourced and reporting bugs is a waste of time) |
|
May 7 |
comment |
Wait for a X window to appear/disappear (in a sane way) @msw I'll have a look at the man page, thanks! |
|
May 7 |
comment |
Wait for a X window to appear/disappear (in a sane way) @StephaneChazelas btrace fails on /dev/sda and /dev/sda1 with 25/Inappropriate ioctl for device |
|
May 7 |
comment |
Wait for a X window to appear/disappear (in a sane way) I'll probably accept an answer teaching me how to measure if the disk is really being waken :) This memlock stuff is new to me! |
|
May 7 |
comment |
Wait for a X window to appear/disappear (in a sane way) @StephaneChazelas they are mounted with noatime, so I guess the disk isn't really being waken, then. |
|
May 7 |
comment |
Wait for a X window to appear/disappear (in a sane way) I'm using fatrace to check for disk wakeups, and it tells me bash reads /bin/sleep and /usr/bin/wmctrl every half second, that's why I'm looking for some program that'll actually wait for window events. Am I missing something? |
|
May 7 |
asked | Wait for a X window to appear/disappear (in a sane way) |
|
May 3 |
awarded | Notable Question |
|
Apr 27 |
comment |
Any programs suitable for making a database over disk-content? I think you are taking the wrong path (the most difficult one). Have you already looked into solutions to manage multiple hard drives like RAID and LVM, and the awesome filesystems ZFS and Btrfs? If not, don't look for anything else! |
|
Apr 15 |
comment |
Can't process stdout with pipe as it comes Right, this is the fix on the tshark part. Although, as I have shown in my own answer, if more than one pipe is going to be used, the others will have to be fixed too. As a simple example, tshark -l ... | grep . | grep . doesn't work, whereas tshark -l ... | stdbuf -o 0 grep . | grep . works, so all information on this thread was useful. Thanks everybody so much for all the help! |
|
Apr 15 |
accepted | Can't process stdout with pipe as it comes |
|
Apr 15 |
revised |
Can't process stdout with pipe as it comes added 28 characters in body |
