210 reputation
110
bio website
location
age
visits member for 2 years, 5 months
seen Mar 3 at 22:23

Aug
25
comment How to sync file times from one directory tree to another
Even when using --existing, there is still some risk loosing modifications made to some files since the duplication. Maybe there is some way preventing rsync from copying content at all? Then the problem would shrink to some resetted timestamps. On the other hand, using rsync without --size-only would give a precise picture of what files would need a new timestamp and which do not. Using with -n for dry run, I would get a list stating >f for files that would be reseted but should not, and .f.t for files that are old and would get the correct old timestamp. But how to apply it then?
Aug
25
comment How to sync file times from one directory tree to another
Looks cool. I also added --existing to prevent rsync copying files again that where deleted after the duplication.
Aug
24
comment cpu load measure with hyperthreading on linux
Simply spoken: How to tell at a given moment, if my CPU would be capable to do further work, without slowing down the currently ongoing work?
Aug
24
comment cpu load measure with hyperthreading on linux
My question is how to get the total usage of available cpu cycles. I think you're saying 'you can't get that value because the OS isn't capable of knowing it', but I am not aware why. The OS may know if hyperthreading happens by probing the behaviour or having some CPU driver defining if the current CPU model uses it or not. In worst case, the OS truely is incapable of handling this, I like to have a suggestion how to compute the value by myself using my knowledge of my current CPU hyperthreading capabilities.
Aug
24
asked How to sync file times from one directory tree to another
Jul
25
comment cpu load measure with hyperthreading on linux
This is obviously a reason why the OS should be aware of virtual cores. So it has to find out and compute the physical core usage based on it. Otherwise the whole concept of measureing "usage" and "load" has no use to the user. If I run top, I usually have some question like "Is the system running at it's limit?" or "Would it be useful to divide the work into more processes?" etc. This questions can't be reliable answered by the current topoutput.
Jul
19
comment cpu load measure with hyperthreading on linux
I just like to have a load measure where 100% would mean that every cycle of every real core is used.
Jul
19
comment cpu load measure with hyperthreading on linux
It seems so, but it doesn't have to? The real vs. virtual core mapping is a simple one to two map. The problem is how to measure load on a virtual core that actually changes its available performance by getting scheduled with another one on the real core. But all data is avalable I think, the question is just where are the tools that get a proper result out of them?
Jun
28
comment Fast and reliable reboot after power loss
This can also be combined with another eg. ext3 read-writable partition where single databases or log files are stored. As this partition is usually small and low on file count, it can be fscked in a short time and is unlikely to fail completely. Even if data gets corrupted, the system boots up, and your applications can be resilent to missing data if well made.
Jun
28
awarded  Scholar
Jun
28
accepted Fast and reliable reboot after power loss
Jun
28
asked cpu load measure with hyperthreading on linux
Apr
13
asked Kernel panic after power loss
Mar
14
asked Most reliable IP resolution in unknown LANs
Mar
10
comment How to make Windows 7 switch between programs faster after a while?
As another example, usual Linux distributions do not swap out anything until the RAM is almost full, which seems to avoid this problem at all. Maybe Windows could be switched to this behaviour too.
Mar
10
answered Fast and reliable reboot after power loss
Feb
17
awarded  Tumbleweed
Feb
16
comment Fast and reliable reboot after power loss
The LiveCD was a good hint.. actually it seems a readonly partition overlayed with a writable tempfs would do the job for 'kiosk'-only uses. The harddisk would be mounted readonly this way, suffering no effects from powering off. So the fs should stay clean and reboot like usual every time. Will try this out.
Feb
16
awarded  Commentator
Feb
16
comment Fast and reliable reboot after power loss
A rock solid solution for presentation applications would be having the harddisk mounted read only, and use OverlayFS or something else to get a read write capable root fs, that only writes to a temporary ram fs. However it seems quite complex to turn a ordinary distribution into such a setup.