bmsync (once working)
Posted: Fri 12 Jun 2015, 07:37
G'day Mike Walsh,
I have not tried bmsync-ing from another Pup on this my multi-Pup main computer to the other computers on my home network. Nor have I booted with another Pup on this machine since the successful bmsync to check if BitMeter is still working on those Pups I have had time to install it to (Friday is minding-the-grandkids day and we've been to the zoo).
So, when I do these checks (soon, now that 'they' have gone home with their mother ), I'll make a back-up copy of the main .db file just before I do anything.
I have only used the basic parameters so far:
- on the 'other computers', just the three command lines entered via the terminal or as a script.
bmdb webremote
bmdb webstop
bmdb webstart
Each line produced an encouraging text response in the terminal.
Still not sure if I should terminally stop the webremote once the data exchange has occurred or just shutting down the other-computer is adequate.
I then switched to my main computer (its IP address is not required (or actually known )). In its terminal, I typed just:
bmsync 192.168.2.xx
(that is, just the other computer's IP address after the bmsync - no extra parameter nor did I try the other computer's puppypc name)
And this added the other computers' BM data to the .db file on my main computer's data partition. When I run it again, I'll check if I see an ERR within the terminal text response as the sync occurs.
This bmsync process reminded me of an app for my wifi-ed android phone that enables it to transfer files to my data partition. The app sets up the phone as a local network server and displays the IP address I need to enter into my computer browser to access the android phone files (photos mostly) so I can download/copy them onto my data partition.
As I see it, BitMeter in sync-ing sets up each 'other computer' as a server of the BM data on it for the main computer as a client to add or update to its .db file.
Plenty to play with still.
David S.
I have not tried bmsync-ing from another Pup on this my multi-Pup main computer to the other computers on my home network. Nor have I booted with another Pup on this machine since the successful bmsync to check if BitMeter is still working on those Pups I have had time to install it to (Friday is minding-the-grandkids day and we've been to the zoo).
So, when I do these checks (soon, now that 'they' have gone home with their mother ), I'll make a back-up copy of the main .db file just before I do anything.
I have only used the basic parameters so far:
- on the 'other computers', just the three command lines entered via the terminal or as a script.
bmdb webremote
bmdb webstop
bmdb webstart
Each line produced an encouraging text response in the terminal.
Still not sure if I should terminally stop the webremote once the data exchange has occurred or just shutting down the other-computer is adequate.
I then switched to my main computer (its IP address is not required (or actually known )). In its terminal, I typed just:
bmsync 192.168.2.xx
(that is, just the other computer's IP address after the bmsync - no extra parameter nor did I try the other computer's puppypc name)
And this added the other computers' BM data to the .db file on my main computer's data partition. When I run it again, I'll check if I see an ERR within the terminal text response as the sync occurs.
This bmsync process reminded me of an app for my wifi-ed android phone that enables it to transfer files to my data partition. The app sets up the phone as a local network server and displays the IP address I need to enter into my computer browser to access the android phone files (photos mostly) so I can download/copy them onto my data partition.
As I see it, BitMeter in sync-ing sets up each 'other computer' as a server of the BM data on it for the main computer as a client to add or update to its .db file.
Plenty to play with still.
David S.