Ben98SentraSE
Rather than go through it line by line just replicate this for your qseti.txt (you may need to adjust the min & max WU's though)on your Win98 PC with modem.(obviously without the ***** in it
)
************************
# work_unit_adjust sets the number of
seti@home.exe client apps
# that are processing work units. This number is used to determine
# how many work units are really outstanding (which is the # in
# the queue, plus the number of clients working on work units)
work_unit_adjust=1
# sync_hour is the hour to connect the seti server to send all
# outstanding results, and to acquire new work units. By default the queuing
# app picks the minute of the hour at random. (The hour is picked
# at randmon as well if the following line is commented out)
sync_hour=3
#sync_min=0
# setting autoconnect to 'no' will stop setiq from attempting to
# automatically contact the seti server. To connect you must use
# sq.exe tools. E.g: sq local connect
autoconnect=no
# startupconnect causes setiq to transfer work when first started.
# Setting this value to 'no' will disable this.
startupconnect=no
# max_poll is the longest amount of time to wait when polling the
# setiserver. This value is in minutes. If setiqueue can not connect
# to seti server, it retries in 1 second and doubles that amount
# each time the connection fails, up to max_poll. This value
# may be set from 5 to 2880.
max_poll=20
# if there are abort_retry_count *consecutive* failures in trying
# to perform an operation to seti server, setiq will disconnect
# and disable autoconnect (if its not already disabled)
#abort_retry_count=8
# queue_depth is the number of days worth of work units to queue.
# the min is 1, the max is 5. This number to queue fluctuates a bit
# as min & max are computed by the rpd (result per day) which is
# tallied as the number of results submitted to the queuing app
# over the last 24 hours.
queue_depth=4
# ave_over is the number of days to average the results over
# to determine the number of work units being completed per day.
# This setting must be within the number of days setiq has been
# running.
ave_over=1
# min_limit limits the minimum queue threshold.
# max_limit limits the maxumum queue threshold. These are used if
# for some reason the queuing app is downloading too many work units.
# This allows an override to reduce the numbers.
min_limit=3
max_limit=8
# This setting will increase the upper limit of the queue size
# to be at least 'max'. The maximum value for this setting is 20.
max=8
# response_delay sets a delay in seconds that setiqueue will wait
# before responding to receiving a new result from a client. Set
# this value to 5 if you are using the seti monitor app. This will
# give the app enough time to see the result.sah file.
# response_delay=5
# result_log provides the location to keep a copy of all results
# ever completed. The file result.log (in the setiqueue directory)
# can be used to see which local machine completed which result.
# Comment this line out if you do not wish to keep a logged copy
# of all results sent. Note the results are logged when clients
# complete, not when they are sent to the seti server
result_log=log
# report_stats disables the reporting of statistics to setiq server.
# At some point I will put a link to get setiq stats on my website, but
# have not completed the web site code to do this yet. The stats also
# are useful when I send mail to s@h to indicate how many seti users
# are using/depending on setiq. And finaly I can send update notices
# to active users whom are reporting statistics when a change is
# made to setiq.exe
#report_stats=no
# After stats are reported an optional local job can be dispatched
# with job=
#job=C:\W2K\system32\cmd.exe /c e:\backup\backup
# log_file sets a filename where setiq output should be logged.
# log_days indicates how many hours to keep in the log before starting a new one
log_file=setiq.log
log_hours=1
# proxy_server is used if the non-queued clients normally work
# through a proxy server. By supplying proxy_server the connection
# setiqueue makes will be through the proxy server & port
# information.
#
# Note: This setting is under testing.
#
#proxy_server=
#proxy_port=80
*********************
Note the # symbol stops that line from having any effect.
You'll need to manually connect to the SETI server to flush the WU's.
Put this line in a .bat file to give you a manual connect 'button'
sq local connect
For the wsockhk.txt replicate this one for the PC which has SETI & SETIQ on it(put it in SETI & SETIQ directory)
***********************************
# qseti_server specifies the local IP address that setiqueue is
# running on. All Seti Server communications are routed to the
# specified system.
#
# If setiqueue is running on a server that does not have a constant
# local IP address, then the format qseti_server=\\ComputerName can be
# used so long as the server is an NT server and the clients have
# the proper access permissions to the server.
#
# IF THIS S@H CLIENT IS RUNNING ON THE SAME SYSTEM AS THE SETIQ.EXE
# PROGARM, THEN DELETE THIS SETTING.
# log sets the filename to write a log of operations occuring.
# this is for debugging.
log=wsockhk.log
********************
Note if you use this as it is you'll need to use the setipatc.exe in a DOS window at the SETI@home directory to patch the SETI client to enable it to connect to SETIQ.Note down the name of the .dll file it says its patched to (will most most likley be Ws2_hk.dll).Copy the wsockhk.dll & rename it to that.Copy them both to the SETI directory
Alternativley in the blank line you could put your LAN cards IP address in it in which case you don't need to patch the SETI client.
For the other Win 98 PC ,put in the IP add of the PC with SETIQ on it.
I think that covers everything
I'm afraid I don't know about the Linux box but
ColinP or Darkone can help you there
>>>>I would also like to have the option of grabbing WU's off my SetiQ server from my boxes here at work so I can log all the WU's I complete. Is that possible as well?<<<<
Yes it is ,but I don't know how
,I'll ask my SETI partner because he was doing it for a short while.I'll see if I can get him to post here(that would be a 1st!
) to help you
Silver black
It is worth having SETIQ even on a 24/7 connection ,as the servers go down from time to time .
Facebook
Twitter