On Sun, 1 Jul 2007, Carlos E. R. wrote:
Don't forget log entries...
Yes, I also checked them, but none was flooded with data nor were there recurring warnings or errors or anything of particular interest.
Notice that simply by watching the log you may cause a periodic write operation: every read means a write of the access time. That's why it is important to dissable it.
For instance "tail -f file" causes continuous writes, but "tailf file" does not. This is documented somewhere.
I would consider this mostly solved for as far as I dare to go without making anything too risky. I've used Linux since SuSE 8.2, so I should already know not to expect things to work as they do on Windows.
Still, letting the disks go to sleep is a good thing, IMO. This "should" work.
I've never managed to get any of the standby modes to work. I've tried using KPowersave on KDE, but asking it to initialise standby mode only causes the system to hard crash: It gets totally jummed after having suspended processes, and cannot be recovered without forcing a hard reboot via the motherboard. Simply commanding a disk to go to standby with hdparm (-y or -Y) spinns them down, but only to be waken up in a minute or so as some data needs to be written. On the other hand, I haven't really researched this, as I nowadays shut down for the night. If standby worked, I wouldn't have to do that, of course. I don't care to try too much, though, as such a hard crash causes some heavy file system check runs on reboot and even forced me to boot on failsafe before I was able to boot normally again. (Normal boot didn't proceed past a certain point, but it was easily fixed.) So I don't want to have those crashes to happen and risk more and more serious problems arising as a result. It would be interesting to try to have the standby work, yes, but trying it out when it doesn't work seems too dangerous. And I mean it really crashes: I tried to SSH to my machine from another one, so as to log in and try and get it up again, but SSH simply timed out, as obviously SSHD, and perhpas the network interface too, had been suspended. Is there any other way to initialise standby than via KPowersave? I wonder if the problem lies in KDE or X. It would be no problem at all if I had to exit KDE and X for standby in case I happened to know I'd be leaving the machine running idle for a couple of hours, or would leave it on for the night so as to avoid daily hard boots. I boot to runlevel 3, then manually start KDE, so I need not init 3 or anything to get out of X. -- Tero Pesonen -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org