Benkas projects

Here you can see the projects that I tried to make... :)

Filename Last changed Description

sf-0.8.tar.gz Feb 17 2004 sf - Spam filter.
Filter out spam entries in mail logs

netcraft.uptime-0.1.tar.gz Feb 6 2003 netcraft-up - Uptime for netcraft.
Makes it possible for Netcraft.com to track uptime on unix-boxen

jedi95-Phoenix-Miner-2b57b96.tar.gz Nov 6 22:10 Phoenix-1.6.2 - Original unmodified Phoenix miner

jedi95-Phoenix-Miner-2b57b96.diff.v7 Oct 22 22:35 Phoenix-1.6.2.1 - Diff against Phoenix miner version 1.6.2
Changes some bits. Implements all the 1.6.2 options as well as the following options
Options:
-2 --use2phase:
Use the modified 2 phase queue worker, described below
-B --showblock:
Show the received number of blocks on status line since this miner started.
-c --showcompact:
Show the status line in compact mode.
-d --showdevice:
Show the platform and device this miner is using on the status line.
-f --showfrequence <freq in sec>:
Set the update frequence in seconds for status line. Not used when -n is active.
-l --logtotext <log file name>:
Log output to the specified logfile. Status are constructed the same way as for on-screen, but are only updated before each new work. This option can be used with the -n option to only log to file and not to any screen. Log file can be rotated externally as it is closed upon every line written.
-n --noshow:
Don't show anything on screen except errors. This can be used to mine using no screen at all.
-P --showlongpull:
Show number of received long pulls on status line (if they are used in pool). This number should normally be one less then shown blocks, but can for several reasons be less. Most obviously, when network is unstable, long pulls can be missed. The miner rely mostly on the new block signal from pool, so this can be seen as an indication of network stability.
-p --showpercent:
Show accepted/rejected work also as percent of received work. If -w is also specified, then that output also have a percentage against received work.
-r --showreceived:
Show received work in status line. This is updated every time requested new work are received or when long pull is received (as it also contain new work).
-t --addblocktime <times>:
Add the times (or more precisely, the last number of blocks) as a comma separated list without any blanks, to do sum on to give average time between new blocks reveived. This adds a smaller window(s) as the average on all blocks received are also shown here as well as the time for the last block.
-v --verbose:
Show a lot of information about the internal workings of the miner. This can be seen mostly as a debug option, as it shows several things not normally needed to get the normal work done. if -l is also specified, information is put on the logfile as well. This can be different information from the one shown on screen.
-w --showwork:
Show a detailed report of the distributions of work, how many contained at least one accepted part (ActW), rejected part (RejW), did not have any accepted part at all (UsvW), was only checked partly and had at that point no accepted or rejected work found (WstW) and work abandoned from work queue and never checked at all (AbnW). When the -p option is used as well, these are also shown as a percentage against received work.
When we use the -2 option, we change the behaviour of the work queue. It starts out by measuring the time the kernel takes to compleate some work, then using that information to delay the request of new work to the end of current check, so that new work normally will be available when the check is done, but not abandon any work if a long pull should be received in the middle of the check. Obviously, if the request for new qork has been sent and also received so we have a queued work and long pull comes in, we must abandon that work as it referes to the previously block, which where just solved anyway. This behaviour is not fully functionary if we use this miner on a very fast rig. As the delay of the request is set to be 5 seconds below the complete check of one work, any rig with a check time of say 10 seconds or less, benefits less from this change as it takes time for the network anyway to deliver new work.
Also, there is an effort to reduce stale work by network misses, as it checks the time it takes to deliver new work as well. If the time is exceeding 5 seconds, it alter the time waiting for new work by decresing the wait time, thus holding work in the queue and also compensating for bad network delivery. This mature over time, so that some network misses are weeded out and delays are set down to 5 seconds again. If there is a major delay, the queue size is upped one to have at least one more work ready at all time. This can happen several times to up the queue several times. This behaviour is also reduced if the time to deliver decreses, even to the point the queue can be shortened down to a length of 1.
A third thing implemented is; if the network goes down for 5 minutes, the connection is closed and reopened again. This is done regardless if we are using a backup pool or not, and the active pool is always connected to. This means that other measurments to handle pool activity (with backup pool) is still in place.

jedi95-Phoenix-Miner-2b57b96-v10.diff Oct 24 14:46 Phoenix-1.6.2.1 - Diff against Phoenix miner version 1.6.2
Changes all the above as well as introducing a new option -N <Network_Delay>. This option adjusts the time to wait until request for new work are made from default of 5 seconds before work is needed to the seconds you specify, down to 1 second. Note that even if we set it to 1 second, this miner checks the network delay on the fly and readjusts it self so it have the work when needed, even if it means that the request should be made sooner then expected.

jedi95-Phoenix-Miner-66287e7.diff.v2 Oct 22 23:16 Phoenix-1.6.4.1 - Diff against Phoenix miner version 1.6.4
Same change for this miner as above. Note: There is some differences between 1.6.2 and 1.6.4, but that mostly has to do with a newer RPCClient.

jedi95-Phoenix-Miner-66287e7-v4.diff Oct 24 14:46 Phoenix-1.6.4.1 - Diff against Phoenix miner version 1.6.4
Changes all the above and also introduses the same -N <Network_Delay> as the -v10 diff above.

Filename	Last changed	Description
sf-0.8.tar.gz	Feb 17 2004	sf - Spam filter. Filter out spam entries in mail logs
netcraft.uptime-0.1.tar.gz	Feb 6 2003	netcraft-up - Uptime for netcraft. Makes it possible for Netcraft.com to track uptime on unix-boxen
jedi95-Phoenix-Miner-2b57b96.tar.gz	Nov 6 22:10	Phoenix-1.6.2 - Original unmodified Phoenix miner
jedi95-Phoenix-Miner-2b57b96.diff.v7	Oct 22 22:35	Phoenix-1.6.2.1 - Diff against Phoenix miner version 1.6.2 Changes some bits. Implements all the 1.6.2 options as well as the following options Options: -2 --use2phase: Use the modified 2 phase queue worker, described below -B --showblock: Show the received number of blocks on status line since this miner started. -c --showcompact: Show the status line in compact mode. -d --showdevice: Show the platform and device this miner is using on the status line. -f --showfrequence <freq in sec>: Set the update frequence in seconds for status line. Not used when -n is active. -l --logtotext <log file name>: Log output to the specified logfile. Status are constructed the same way as for on-screen, but are only updated before each new work. This option can be used with the -n option to only log to file and not to any screen. Log file can be rotated externally as it is closed upon every line written. -n --noshow: Don't show anything on screen except errors. This can be used to mine using no screen at all. -P --showlongpull: Show number of received long pulls on status line (if they are used in pool). This number should normally be one less then shown blocks, but can for several reasons be less. Most obviously, when network is unstable, long pulls can be missed. The miner rely mostly on the new block signal from pool, so this can be seen as an indication of network stability. -p --showpercent: Show accepted/rejected work also as percent of received work. If -w is also specified, then that output also have a percentage against received work. -r --showreceived: Show received work in status line. This is updated every time requested new work are received or when long pull is received (as it also contain new work). -t --addblocktime <times>: Add the times (or more precisely, the last number of blocks) as a comma separated list without any blanks, to do sum on to give average time between new blocks reveived. This adds a smaller window(s) as the average on all blocks received are also shown here as well as the time for the last block. -v --verbose: Show a lot of information about the internal workings of the miner. This can be seen mostly as a debug option, as it shows several things not normally needed to get the normal work done. if -l is also specified, information is put on the logfile as well. This can be different information from the one shown on screen. -w --showwork: Show a detailed report of the distributions of work, how many contained at least one accepted part (ActW), rejected part (RejW), did not have any accepted part at all (UsvW), was only checked partly and had at that point no accepted or rejected work found (WstW) and work abandoned from work queue and never checked at all (AbnW). When the -p option is used as well, these are also shown as a percentage against received work. When we use the -2 option, we change the behaviour of the work queue. It starts out by measuring the time the kernel takes to compleate some work, then using that information to delay the request of new work to the end of current check, so that new work normally will be available when the check is done, but not abandon any work if a long pull should be received in the middle of the check. Obviously, if the request for new qork has been sent and also received so we have a queued work and long pull comes in, we must abandon that work as it referes to the previously block, which where just solved anyway. This behaviour is not fully functionary if we use this miner on a very fast rig. As the delay of the request is set to be 5 seconds below the complete check of one work, any rig with a check time of say 10 seconds or less, benefits less from this change as it takes time for the network anyway to deliver new work. Also, there is an effort to reduce stale work by network misses, as it checks the time it takes to deliver new work as well. If the time is exceeding 5 seconds, it alter the time waiting for new work by decresing the wait time, thus holding work in the queue and also compensating for bad network delivery. This mature over time, so that some network misses are weeded out and delays are set down to 5 seconds again. If there is a major delay, the queue size is upped one to have at least one more work ready at all time. This can happen several times to up the queue several times. This behaviour is also reduced if the time to deliver decreses, even to the point the queue can be shortened down to a length of 1. A third thing implemented is; if the network goes down for 5 minutes, the connection is closed and reopened again. This is done regardless if we are using a backup pool or not, and the active pool is always connected to. This means that other measurments to handle pool activity (with backup pool) is still in place.
jedi95-Phoenix-Miner-2b57b96-v10.diff	Oct 24 14:46	Phoenix-1.6.2.1 - Diff against Phoenix miner version 1.6.2 Changes all the above as well as introducing a new option -N <Network_Delay>. This option adjusts the time to wait until request for new work are made from default of 5 seconds before work is needed to the seconds you specify, down to 1 second. Note that even if we set it to 1 second, this miner checks the network delay on the fly and readjusts it self so it have the work when needed, even if it means that the request should be made sooner then expected.
jedi95-Phoenix-Miner-66287e7.diff.v2	Oct 22 23:16	Phoenix-1.6.4.1 - Diff against Phoenix miner version 1.6.4 Same change for this miner as above. Note: There is some differences between 1.6.2 and 1.6.4, but that mostly has to do with a newer RPCClient.
jedi95-Phoenix-Miner-66287e7-v4.diff	Oct 24 14:46	Phoenix-1.6.4.1 - Diff against Phoenix miner version 1.6.4 Changes all the above and also introduses the same -N <Network_Delay> as the -v10 diff above.

This file was last modified: Nov 6 22:11

Supports