This one will ask you where, & how you want to set up a common shared database:-Ġ.7.6 for 32-bit (w/database installer):. The latest versions, for those of us who want to run BitMeter on multiple Puppies & get a monthly aggregate total. pets are now mirrored at can never have too much backup! Links are as follows:. Is that possible? Is my intention clear, what I want to do?īitMeter CPU usage.jpg 'Spike' every 10 seconds. Is it possible, via Samba, to remotely open a terminal in 'Pupshare', using Rox (right-click in the Rox-filer window, and 'Terminal here')? If so, then I could switch off the Compaq's BitMeter daemons from the Dell.so at least I could do things all from one end. Be nice if I could automate the process, but as I know absolutely nothing about scripting, this means relying on someone else to do this for me.which is, I feel, asking a bit much!Įven David's suggestion would, if amigo is correct, mean briefly switching off the bmcapture daemon while the database was being updated.ĮDIT I'm going to pose a question now. Either David's suggestion.to use a copy of the main 'bitmeter.db' file for the duration of each session on the Dell, and then to write it back at the end of the session or, which I'm inclined to think would also work, to switch off the bmcapture daemon manually on the Compaq when I want to use the Dell, so that only the Dell is, at that point, writing to the database.īoth of these mean manual intervention. (See attachment).īUT the database is very obviously not being updated. Observing pWidgets' CPU graph (which I use), instead of solid 100% usage, I now merely get a nice little 'spike' every 10 seconds or so.which is what I would expect. Having repeated the experiment with the monitor refresh interval increased to '10', the same as the others, the CPU usage is now far more reasonable. If amigo is correct (and I'm inclined to think that he/she is ), then the 'file-lock' will prevent the secondary 'write' from occurring. This means, of course, that whenever I attempt to use the Dell at the same time, I have at least two BM-OS installs attempting to write to the main database simultaneously. I'm inclined to think amigo is right about the file-locking.īy the very nature of the way we have this set-up, whichever Puppy I happen to be running, BitMeter is set to start automatically, and to use the sym-linked remote main BitMeter database as it does so. Of course, my reasoning could be fallacious.but I've a feeling that's somewhere near the root of the problem. So later on today, I'm going to repeat last night's experiment, and make some adjustments to the refresh intervals. I don't for a moment believe that it's the Samba connection itself, since when I'm on the Dell, the Compaq's 'Pupshare' is one of the first things I open it stays open for the duration of the session, and CPU usage is almost always what you'd expect it to be perfectly average. The two that I'm interested in are the 'Summary' and 'Alert' tabs. Once every second.! I don't actually use the 'Monitor' tab at all.nor the 'History' tab. I think that the Monitor tab refresh interval is the culprit. From a 'virgin' install of Bitmeter, they read as follows:. I've been thinking that the main reason, probably, that the P4 is running flat-out is in all likelihood due to the frequency of the 'Refresh Intervals' (set via the BitMeter 'Preferences' tab). So, yes for the few occasions on which I use the Dell, yours is actually quite a practical You could well be correct about the 'file lock' I certainly won't dispute that, since I'm still fairly new to Linux. and I can now read/write in both directions.
0 Comments
Leave a Reply. |