One thing that I like on this forum is the variety of things which I can offer and purchase from people via the market area. As you can see from my signature, I'm a bit of a Jack-of-all-Trades, offering mining contracts, shell scripts and currency exchanges.

My main issue is that despite my signature being fairly small (two lines on a decent resolution screen) I can't expand it, meanwhile some people's signatures are far larger (screen real-estate wise) but within the limits.

I think that on a forum, the best measure of a reasonable signature is vertical pixels, not characters, so I'd like to propose limiting the signature to say four or five line rather than by number of characters. In my opinion, this would be better for traders like myself, and would better limit the actual imposing signatures (those few with large images or a lot of lines).

Would like to know what other people think.

10 minutes is pretty impressive, took me at least an hour.

Posting pics would give you some more legitimacy I expect. Good luck selling anyway. ^^

Oh OK, I do this instead on my laptop to monitor everything:

mineco.in is my personal favourite right now. It pays out absolutely everything including transaction fees.

If it's anything like on Linux, you need to cd to the directory Phoenix is in before running it.

I agree with you, I have no issue with unions as long as:

• They aren't supported, nor granted power, by states
• They aren't breaking terms of existing contracts

By the latter, I mean striking when you've agreed to do 40 hours this week is out of order. If people want the right to strike, they need to get it into their contracts.

Mineco.in pays out the full amount.

Wuked, can we get a JSON API for workers so that we can check if our miners are still submitting shares?

I'd use it if it supports mineco.in and eligius.

I do on ssh, this loads the miners into screen sessions so you can load them up via SSH on $identifier[0]-miner, $identifier[1]-miner etc. You can do the same with temperatures, screen is called temps.

So just ssh in and hit:

screen -x temps

OR

screen -x Radeon5850-1-miner (assuming one of your identifiers is Radeon5850-1).

Glad to be helping people out, I'm uploading v0.2 right now and adding it to first post.

Triple HD 5850s at 966/185 doing 385MH each stable.

Waiting for my bigger fans to arrive tomorrow and might try 1000/185.

Yeah I'm just doing a check for GPU load below 90%, then sleeping 15 sec to make sure it's not an anomoly, then killing the miner and changing to backup pool if it's not fixed.

Also, version 0.2 should be up soon, with regular status reports to the main window so that you can see everything is mining, removing the annoying 'All seems fine' message every 2 minutes, and timestamps in the main window.

I'm selling 650m for 1 BTC and buying 900m for 1 BTC. I'm not sure how you can buy it low and sell it back to me.

If you mean buy from someone else and sell to me, you can do that.

I'm just detecting GPU load via aticonfig --adapter=X --odgc and killing GPUs which aren't under load.

Also, yeah this works for headless I guess, screens are named $identifier-MINER so if you set an identifier to 'Radeon5850' the screen would be called 'Radeon5850-MINER'. Temp screen is called 'temps'.

Back up with new prices. Yes, I'm still selling ISK.

Autominer 0.3.2.6 - New Interface Baby!

I decided to redo the thread from scratch to better explain Autominer. I felt that the old thread rambled a bit and didn't explain enough, so this one should be better designed to take care of the users' needs.

About Donate Mode

A few people were saying they'd like to donate but have no BTC up front, so if you want to, just edit common.lib (on v0.3.2.3 or above) and put the following line at the bottom:

donateMode=1

It will automatically give me 1 out of every 200 mining cycles (0.5% of your mining time). I will implement an option later so you can decide how much to donate.

This option is off by default, it's purely optional, and thanks if anyone decides to use it.

Download Autominer v0.3.2.6




What is Autominer?
Autominer is a bash script (technically, a set of bash scripts) written to automate the process of mining on a Linux rig. After a relatively short configuration time, you can just type a single command to start mining on all of your GPUs, in screen sessions for remote monitoring, with a temperature monitor and automatic pool monitoring and swapping in the case of downtime. Interested? Good.

And some history...

v0.3.2.6
- Bug fix of the checkphoenix.sh script (it was connecting to the wrong pool)
- Bug fix in screen settings

v0.3.2.5
- Added a 'countTarget' variable to change the frequency of 'successfully mining' updates
- Added a checkphoenix.sh script for diagnostic purposes
- Added better output to configure.sh when no workers are chosen
- Fixed a bug that was causing configure.sh to ask about donateMode for each GPU

v0.3.2.4
- Fixed a bug in configure.sh where it was writing Worksize variable to queuesize.
- Cleaned up configure.sh

v0.3.2.3
- Fixed a bug with the 'kill process' function.
- Cleaned up some text outputs.
- Added getting the CHANGELOG when using an outdated version.
- Fixed the loop function in the main program.
- Added 'donation mode' (optional, of course). To donate 0.5% of your mining to aid Autominer
development, just add 'donateMode=1' to common.lib. This will cause one in every two hundred cycles
to be donated.

v0.3.2.2
- Added support for PLATFORM in Phoenix.

v0.3.2.1
- Fixed a bug which caused pool switching not to work on machines with both monitoring modes enabled
if the downtime was picked up by GPU load first.

v0.3.2
- Added support for hashrate-based pool downtime detection in addition to GPU-load based, works even
if overdrive won't report GPU load (it's an issue for some people with risers) - needs XML RPC enabled
- Fixed a bug with downloading 'LATEST' file

v0.3.1
- Added experimental support for thejfk's getRate.py hack to display hashrate in miner window
- Rewrote the entire interface to use a single screen window, takes some getting used to

v0.3
- Added defaults files in order to avoid overriding a user's config upon update
- Added warning and disabled pool monitoring if GPU load can't be found (previously caused error spew)
- Added a stopmining.sh script which should look through screens and kill all Autominer screens
- Added detection for obsolete versions
- Added an experimental configuration script
- Removed version numbers from several script headers
- Moved opening the temps window to the main script
- Changed the temps window so that height corresponds to number of GPUs

v0.2
- Added status update to monitor where cards are mining and if cards are mining
- Added timestamps to output in main window

v0.1b
- Added support for phoenix failures, added workers

v0.1
- Got it working


What does Autominer need?
Autominer needs a relatively standard set of Linux tools, plus a mining program, those are:
tar - To extract the archive in the first place
wget - To check for updates to the package
screen - For monitoring sessions
xterm - To load the terminal windows themselves
phoenix-miner - To mine delicious coins!

To get this short list of tools (other than Phoenix, that's here in the forum) in the main distros is easy, fire up a command line and type:

Ubuntu Natty: sudo apt-get install screen tar wget xterm
Debian: sudo apt-get install screen tar wget xterm
Arch Linux: pacman -S screen tar wget xterm
Gentoo: emerge screen tar wget xterm

In addition, you need to be running X11 in order to take advantage of ATI Overdrive & multiple Xterm windows, and you need a few minutes to go through configuration the first time you run it.


So, how do I install it?

Well, download the tar.gz file at the top, then go to your favourite command line and navigate to where you put it. Do:

tar xvfz Autominer-x.x.tar.gz (where x.x is the version number)
cd Autominer
./configure.sh

Follow the instructions in the configuration script, assuming it works it will spit out two files called cards.lib and common.lib, with all the information you put into the script contained in them.


I'm running Autominer, how do I update it?

If your existing version is 0.3 or above, follow these instructions. If you're on 0.1, 0.1b or 0.2, you'll need to remove your existing Autominer & follow the install instructions as above. This is because 0.3 changed the file structure and the variable names, and is fairly incompatible with lte v0.2 config files.

Assuming you're running v0.3 already, simply download the .tar.gz and extract the files into your Autominer directory. This will not overwrite cards.lib or common.lib, as I have modified the file structure to preserve these files which contain your settings.


How do I *RUN* this beast?

First of all kill any miners you have open, then go to the Autominer directory and run ./startmining.sh /path/to/Autominer

Controls for the window:
F1-F6 = Windows 0-5
F7 = Previous window
F8 = Next window
Ctrl-a then a number = That number window
Ctrl-a then d = Detach screen (keeps miner running)


You have MH/S in your 'amm' window... how do I get that?

This technique relies upon a patch to Phoenix developed by thejfk, but it's relatively easy.

1. Open up a command line
2. cd to your phoenix directory
3. wget http://robertlacroix.com/files/phoenix-xmlrpc.diff
4. patch -p0 < phoenix-xmlrpc.diff
5. Send thejfk a tip: 1EhQ1dbeZnxs7wZKngegsHLheAjUK37k7m
6. cd to your Autominer directory
7. Edit common.lib, at the bottom write on a new line:
xmlRPCEnabled=1;
8. Start up your miner, the rest should happen automatically


And how do I monitor it over ssh?

If you want to open over ssh, do DISPLAY=:0 ./startmining.sh /path/to/Autominer

Connect to the screen using screen -x amm -p 0


So, what happened to the file structure?

Previously, whenever you updated Autominer, it came with a new cards.lib and common.lib, this meant you had to re-configure everything every time. Now, I've created files called cards.defaults.lib and common.defaults.lib.

These files allow me to define new variables without overwriting the variables you've saved in your configuration scripts. Obviously, you shouldn't edit the defaults files (they'll be overwritten when you update) but if you want to change something in there, simply copy the variable into cards.lib or common.lib and change it there.

Variables in cards.lib and common.lib OVERRIDE those in cards.defaults.lib and common.defaults.lib. The only time the defaults will be used is if something isn't defined in YOUR config settings.


Can I still manually modify the .lib files?

Sure can. Just copy cards.sample.lib to cards.lib and common.sample.lib to common.lib and modify. Don't edit the defaults, they will be overwritten when you update again.


Common Problems & Troubleshooting

Computer clearly mining but autominer won't connect to the display - Often caused by starting an identifier name with a number. Check your identifier names start with a letter.

Sounds like a plan, I soon plan to start offering rigs as well to UK & EU customers.

OK, a few observations:

1. You said "you get daily BTC transfers in amount of statistical expectation of daily bitcoin generation" which implies your service is zero-variance, but you also talked about a physical rig generating. Can you confirm if the service is zero-variance or direct RPC generation?

2. You claimed 'cheapest price' in your thread title but it isn't true. I offer ~1,110MH/sec rigs for $498.33 per month on three month contracts.

3. You've just copy-pasted half of Vladimir's thread.

I really hope that you reconsider how you go about doing business. If English is not your first language, consider hiring somebody to rewrite your text in legible English for the consumer. If your statements aren't confirmed true, you shouldn't make them.