Post
Topic
Board Mining (Altcoins)
Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0018
by
fullzero
on 17/07/2017, 16:58:46 UTC
All once again good afternoon!

I added:
1. email alarms (sendemail),
2. webUI for monitoring (apache2 + go + gotty),  
# All needed apts will install in first boot if $GOTTY="YES" || $EMAIL="YES". in settings.sh
3. auto update pasteBin and restart miner if something changes.
# you need to run crontab -e and add "*/5 * * * * ~/update_wallets.sh" . To check update every 5 minutes.


Completed / redone:
1. Option to set all Target temps and PowerLimits in two strings while using autoFANS
2. add specific PL and CLOCK for some coins
3. output nvidia-smi to screen every 30 sec when check fans, even if the fans are in manual mode. (to see temps, RPMs, memory in gotty, or via SSH, or via local quake)
4. Manual setting WORKER_NAME to use with pools. In settings.sh . If don't set using nvXXX (last digs of ip)
5. WORKER_NAME is hostname of rig, for more useful network search.

I divided the code into several files (start, miner, overclock, e-mail, fans). Settings rendered in 3 separate files:
settings.sh - constant machine settings
gpus_settings.sh - constant settings of video cards
wallets - settings of wallets, miners, machine settings variables.
Unfortunately, I have not yet had a chance to check how it works on the v18, but on v17 all is good. I think I can check in the next couple of days.

All the files are added to the folders as in the archive. Your need to change autostart from "gnome-terminal" to "~/start" (sudo nano ~/.config/autostart/webmob.desktop )
Settings are given in three files in the mnt sub folder. settings, gpus_settings, wallets

I would be happy if someone at least a small part of my work is useful.

fullzero and other developers: I ask for applications for deleted comments and descriptions, maybe even in some places copyright. While working on the code - some parts were in the way.

Of course, I could forget or confuse something, but I seem to remember everything and wrote.

Please do not make alternate releases.

As I have already told you:

https://bitcointalk.org/index.php?topic=1854250.msg20058141#msg20058141

Quote
In general I would like to offer as many options to members as possible and encourage members to share their customizations.

With any contribution, so long as it is not a blatant copy of a prior contribution; I will integrate it and add acknowledgement and BTC donation address to the top of oneBash.

If you use or make an executable; you must provide me with the source code and I will examine and compile it myself.

Your contribution must be free and open source.

I would like to avoid solutions involving the installation of multiple programs or services; to so something that can be done via SSH, SFTP, or a socket.


also see:

https://bitcointalk.org/index.php?topic=1854250.msg20093039#msg20093039


Quote
You can make modules to do distinct operations: like overclocking, miner selection, watchdog, monero mining, etc to make easier to tune/restart some parts.  And I will integrate them with switches to be readinto / not used in oneBash.  In addition they could also be used independently, such as a OC bash could be run while already mining.  A benchmarking bash / py could be made to find and log the opt stable settings ect.  The goal is to provide members with as many options as possible while maintaining ease of use.

Once most of the requested features have been implemented; I will make a github and target oneBash optimization.


It makes no sense to have members downloading multiple versions of the OS when only a few files are changed.  

Also; in such cases: I cannot confirm that the system has not been altered or malware added ( I am not saying you have done this, but that it is always a possibility especially when done by new members).  


If you post the code for each additional file (or send me a pm with it); I will integrate your contributions into 1bash (or selectively in 2unix depending on how different they are) with a single or multiple switches: and add acknowledgement and your BTC donation address to the top of 1bash.

I was not going to make an alternative release.
I posted the code I redesigned so that you could see and add the options you liked to your release.
I can not put it in separate pieces of code, because this is your code divided into different files, plus my code, plus the code of other developers, a little finished. If interested, download the archive and watch. If you want I can lay out the text files without an archive. https://drive.google.com/drive/folders/0B8OLYcDXEG6rVTdIYmtFMndPdXc?usp=sharing If not interesting, do not use and do not add to the release.

My bad;

Thanks for sharing your implementations.  Smiley

I looked over your files quickly.

I like a number of your methods, as well as your email and gotty modules.

The way you have set this up will make a sense to CS, but I think having multiple configuration files like this might be more confusing to many members.

I do think there should be an easy way for members to keep their OC / addresses / settings when updating to a newer 1bash.  A modification of some of your methods might be the opt way to implement this.

I will integrate a lot of this into v0019.   Smiley

Before then;

Will you modify the email module to be a single file which: conditionally checks if installed prior, if not installs, if installed executes email based on arguments or files read in?

Basically an email function.

Assume; I would add the email variables to 1bash (other than the email password; this read in from  /home/m1/5_email_password )

Let me know.