From owner-freebsd-mobile@FreeBSD.ORG Tue May 27 12:35:56 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8FFC337B40B for ; Tue, 27 May 2003 12:35:56 -0700 (PDT) Received: from pimout4-ext.prodigy.net (pimout4-ext.prodigy.net [207.115.63.103]) by mx1.FreeBSD.org (Postfix) with ESMTP id 86E3B43FD7 for ; Tue, 27 May 2003 12:35:55 -0700 (PDT) (envelope-from metrol@metrol.net) Received: from metlap (adsl-67-121-60-9.dsl.anhm01.pacbell.net [67.121.60.9]) h4RJZsl8100200 for ; Tue, 27 May 2003 15:35:54 -0400 From: Michael Collette To: FreeBSD Mailing Lists Date: Tue, 27 May 2003 12:35:06 -0700 User-Agent: KMail/1.5.2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200305271235.06569.metrol@metrol.net> Subject: When do files syncronize? X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 May 2003 19:35:56 -0000 Here on this Thinkpad T23 I normally just Fn-F4 to put it to sleep when moving it from work to home. This had been working pretty well, with an occasional lock up still happening. That much is a pretty well known problem. This last Friday I did the usual Fn-F4 and brought my lappy on home. What I didn't do was plug it back in until late Sunday. Bad move, as my battery is starting to get on the weak side here. Sure enough, lost power while it was in sleep mode. Powering back up the system went through the usual post-crash fsck. Everything looked cool until I started up KMail. Lost the entirety of my mail settings, which were anything but trivial. I wrote up a pretty bitter bug report over on KDE's site. I really wasn't in a good mood when this happened. http://bugs.kde.org/show_bug.cgi?id=58954 I then mentioned this problem on the KDE-FreeBSD mailing list. I got some advice there to turn off all write cacheing via loader.conf. Now that's done, my system seems to be a little bogged, but not too horribly bad. With my sob story out of the way, here's my questions... When this here Thinkpad goes into a sleep mode, is there any chit chat with the OS to be sure and syncronize any outstanding writes? Would it be wiser to initiate going into sleep via software, such as KDE's laptop app or some other method? Is there any difference? Is there some way to force outstanding writes to clear their buffers before I put this box into sleep mode? At some point I'd like to turn on write cacheing again. I REALLY don't feel comfortable about it at this time though. Is there some way to get a feeling of comfort back with this feature? Later on, -- "Always listen to experts. They'll tell you what can't be done, and why. Then do it." - Robert A. Heinlein