-
How to run the Client
From the readme.txt file
Code:
How to use the Lifemapper command-line client (v. 1.0.00)
================================================
1. Create an account on Lifemapper website at www.lifemapper.org.
The registration form can be accessed through the menu
"Individual Members->Register".
2. Unpack the installation package in a newly created (empty) directory.
To install the client files, extract them from the .zip file using
the compression utility of your choice (WinZip, EasyZip, etc).
On Linux, uncompress the .tar.gz file using the following command:
tar xvfz <installation-file>
Replace <installation-file> by the name of the installation archieve
that you downloaded.
3. Run the executable.
usage (windows): lifemapper_cmd.exe
usage (linux): ./lifemapper
Options:
-q: quiet mode
-h: displays usage message
-e <email>: log in to server using <email>
-c <jobs>: always try to keep <jobs> cached locally
-x <proxy>: use specified proxy server
proxy format: http://[user[:password]@]http_proxy_address[:port]/
-p <priority>: set process priority
* Valid priorities under Windows systems:
32: Normal priority
64: Low (idle) priority
128: High priority
256: Real time priority (not recommended)
* Valid values for priority switch under Linux/Unix are in the interval
-20 to 20, where -20 is the highest priority and 20 is the lowest.
Only root has rights to set priority with negative values.
-
If you run the command line client in windows you must use the priority switch.
-p 64 for 9x and NT4
-p 16384 for 2K/XP
If you don't the client runs at above normal priority and makes the PC unresponsive.
-
So far, on XP with an xp2600, I'm using -p 64 and it's doing 'ok'.
This is a home boxen, so work boxen might be different ...
Thanks for the tips! :thumbs:
-
From the Possams Forum.
Fun with switches:
The Command line client is currently set to normal processing speed, which bogged my system down way to much and interferred with other programs.
For those that havn't played with switches much. Just right click on your shortcut icon and than properties add what ever switch you may want to add after the .exe in the area marked Target: (you can ignore the Open In:)
TARGET: C:\where it is\lifemapper-i386-win-1.0.00\lifemapper_cmd.exe -p 64 -c 9
What I did above was lowered the processing setting to Low (-p 64 ) and set the cache to 9 (-c 9) catch setting can be up to 20 max, but due to a bug they are recomending 9.
If you make a mistake playing with the switches, don't sweat it because the most harm you can do is it won't work and if all else fails just create a new short cut.
Here are the different switches you can use.
Options:
-q: quiet mode (does not give you update messages)
-h: displays usage message
-e <email>: log in to server using <email>
-c <jobs>: always try to keep <jobs> cached locally
-x <proxy>: use specified proxy server
proxy format: http://[user[:password]@]http_proxy_address[:port]/
-p <priority>: set process priority
* Valid priorities under Windows systems:
32: Normal priority
64: Low (idle) priority
128: High priority
On XP and Win2K there are additional priorities:
16384: below normal
32768: above normal
* Valid values for priority switch under Linux/Unix are in the interval -20 to 20, where -20 is the highest priority and 20 is the lowest. Only root has rights to set priority with negative values.
-
tis a bit jerky with 64, going with your recommendation of 16384 on this XP boxen :thumbs:
-
how do you turn it off? (safely, without messing it up/losing work)
-
If you are running it in a CMD window Control C shuts it down.
Starts up where it left off no loss of work.
If you are running it as a service with srvany, stopping the service in the services
applet is ok and using the net stop command works ok.
Starts up where it left off and no loss of work.
-
thanks
these stats are near real time? i am already on the board
maneuvering through the stats is a bit tricky though
-
How are you viewing the stats ?
Stats update twice a day 9am and 9pm
You can get real time stats from the lifemapper website by viewing your profile
but this puts a strain on the already overworked DB server so dont do it to often.
If you are running in a cmd window you get a near real time update everytime the client downloads a new wu.
-
LM as a service
If you want to run LM on a pc all the time (with or without someone logged in), then you can run LM as a service. Here is how I ran the LM as a service:
1 - Extract the LM files to a directory on your pc (C:\Program Files\lm in this example). Run the cli and set up your account info.
2 - Place a copy of instsrv.exe and srvany.exe into your LM directory. These files are used to create and run services. (I forget where I found these files.)
3 - Create 3 new files in the same directory: lmsvc.bat, lmsvc_remove.bat, and lm.reg. Here is the text for each of these files:
lmsvc.bat
----------
c:
cd\
cd Program Files
cd lm
instsrv lm c:\progra~1\lm\srvany.exe (Creates lm service)
pause
call c:\progra~1\lm\lm.reg" (Imports registry entries)
pause
net start lm (Starts the service)
pause
----------
I put the pauses in just so I could visually verify that all steps worked properly.
lmsvc_remove.bat file: (just in case you want to remove the service at some point)
----------
c:
cd\
cd Program Files
cd lm
instsrv lm remove
pause
----------
lm.reg file:
----------
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lm\Parameters]
"AppDirectory"="c:\\progra~1\\lm\\"
"Application"="c:\\progra~1\\lm\\lm.exe"
"AppParameters"="-c 10 -f -p 64" (Whatever parameters you prefer)
----------
4 - Just navigate to the directory where you saved the files and double-click lmsvc.bat. This will install LM as a service and have it start automatically when the pc boots up.
* You will have to edit the path in the .reg and .bat files if you use a directory other than C:\Program Files\lm.
I ran this on 100 Windows 2000 machines for a month and never experienced any problems. The users didn't even know it was running. :walking:
I hope this helps somebody! :banana:
Geier
