Welcome to the PiMP Mining Community Forum.


Coin/crypto news, miner.farm and getpimp.org announcements, guides, and tips.


User editable files for startup and configuration



  • Overview

    The OS counts a number of editable startup files.
    in the terminal use nano the crontab, startup.sh and the gpu-config.json can be found in the root folder of your miner.

    How to edit text files

    There are 3 main editors used with PiMP: nano, vim, and leafpad.

    You can also now make edit (an alias to pimp --edit) command use your editing program of choice.

    To change the default editor for the PiMP edit command:

    1. In the terminal, nano +15 /root/.bashrc
    2. Change the line to the editor you want to use. Examples:
    • export EDITOR=nano Use the nano editor (default)
    • export EDITOR=vim Use the vim editor
    • export EDITOR=leafpad Use the leafpad GUI editor (requires you to use local GUI and/or RDP to see the editor)

    0_1505915463536_pimp-nano-bashrc.png

    1. This will take effect on reboots or new SSH / Terminal sessions right away, but if you want to load it in the current session, you can reload your .bashrc with: source .bashrc

    User editable files

    /etc/crontab

    This lets you schedule a task to run on a regular basis, such as once a day or once a week. We have put info in the file explaining what to change if you want to change something.

    By default, /etc/crontab will run /root/startup.sh on each boot up.

    /root/startup.sh

    This file lets you set most things you want in the startup when your rig boots.
    Like what miner id to start and a sleep function that lets the system get ready before mining.
    also found in here is a 1,2,3 on the how to use the gputool.

    Here is an example:

    # /etc/crontab: system-wide crontab
    # Unlike any other crontab you don't have to run the `crontab'
    # command to install the new version when you edit this file
    # and files in /etc/cron.d. These files also have username fields,
    # that none of the other crontabs do.
    
    SHELL=/bin/sh
    PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
    
    #####################################################################
    # HOW TO SCHEDULE JOBS IN CRONTAB:
    #####################################################################
    
    # +---------------- minute (0 - 59)
    # |  +------------- hour (0 - 23)
    # |  |  +---------- day of month (1 - 31)
    # |  |  |  +------- month (1 - 12)
    # |  |  |  |  +---- day of week (0 - 6) (Sunday=0)
    # |  |  |  |  |
    # *  *  *  *  *  command to be executed 
    
    # In other words:
    # 1. Minute when the process will be started [0-60]
    # 2. Hour when the process will be started [0-23]
    # 3. Day of the month when the process will be started [1-28/29/30/31]
    # 4. Month of the year when the process will be started [1-12]
    # 5. Weekday when the process will be started [0-6] [0 is Sunday]
    
    # FOR INTERVALS:
    # Use the division bar (slash) to divide it up.
    # all x min = */x
    # example: 0/15 in minute column would be every 15 minutes.
    
    # 5 8 * * 0 will run the job every sunday at 8:05 am.
    
    # For more information and a neat calculator, see https://crontab.guru/
    
    #####################################################################
    # USER EDITABLE SETTINGS
    # Use: nano /root/startup.sh to change your boot settings.
    #
    #####################################################################
    
    # COMMANDS RUN ON BOOT UP:
    # To run scripts on reboot, use: @reboot root /path/to/executable
    # If you get "permission denied" run: chmod +x /path/to/executable
    # It is best to edit the on-boot stuff with: nano /root/startup.sh
    
    @reboot root /root/startup.sh
    
    # COMMANDS RUN ON A SCHEDULE:
    
    # Reboot automatically every 6 or 12 hours:
    # 0 /6 * * * sync && echo b > /proc/sysrq-trigger
    # 0 /12 * * * sync && echo b > /proc/sysrq-trigger
    
    # This will reboot at 1 AM Zulu (Rig local time):
    # 0 1 * * * sync && echo b > /proc/sysrq-trigger
    
    
    
    #####################################################################
    # DO NOT EDIT BELOW THIS LINE 
    #####################################################################
    # m h dom mon dow user	command
    17 *	* * *	root    cd / && run-parts --report /etc/cron.hourly
    25 6	* * *	root	test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
    47 6	* * 7	root	test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly )
    52 6	1 * *	root	test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.monthly )
    

    /root/gpu-config.json (which is part of gputool)

    This file is created by gputool --config and is in the JSON format. It allows you to control fans/clocks/power usage.

    More info on gputool can be found in the gputool guide here:
    https://forum.getpimp.org/topic/31/gputool-how-to-overclock-nvidia-and-amd-gpus

    /opt/confs/.conf and /opt/confs/.pcfg

    These files are for the Managed Profiles integrated in the OS These files are setup for you by default to test out if your miner is setup correctly. We encourage to run these as-is first because of that.

    For more information on setting up Managed Profiles: https://forum.getpimp.org/topic/10/setting-up-miner-profiles

    /root/.userrc

    This file is where you can safely put any shell related customizations that may normally be used in .bashrc. We provide a .bashrc that is customized for PIMP, and update it automatically via pimpup, which means any changes to this file will not be preserved, but in it we source the file /root/.userrc where you can put your shell variables safely, and we will not overwrite them.



  • My startup.sh file just got cleaned. Where I can find a fresh one? The link to it in the beginning of the page is a dead end. Thanks



  • The startup.sh file is not changed by pimpup, but the new version is given as startup.new.
    This is so that pimpup will not overwrite a users changes.
    Run pimpup and then you can cp startup.new startup.sh to use that as a base line to make your startup.
    Also the new one has the correct timings, 20 and 25, for clocking and starting.



  • So, how do I run 2 instances of CCMINER so I can mine XVG and AEON concurrently?

    So I can have:

    nvidia.ccminer.aeon.pcfg controlling the AEON mining credentials on NVIDIA GPUs 0,1,2,3 using cryptolight algo.
    nvidia.ccminer.xvg.pcfg controlling the XVG mining credentials on NVIDIA GPUs 4,5,6,7, using x17 algo.
    I have already configured both. But I cannot run them side by side.



  • the syntax in the example settings is incorrect for the

    COMMANDS RUN ON A SCHEDULE:

    Reboot automatically every 6 or 12 hours:

    0 /6 * * * sync && echo b > /proc/sysrq-trigger

    0 /12 * * * sync && echo b > /proc/sysrq-trigger

    Correct Syntax is:

    0 */6 * * * sync && echo b > /proc/sysrq-trigger

    0 */12 * * * sync && echo b > /proc/sysrq-trigger

    Of course to enable either of these you need to take the '#' comment character out. But the main thing missing is the *, if you omit that, you break your crontab and it wont do anything.


  • Support

    Thanks for helping out! We'll get this corrected for the next version.

    PiMPs helping PiMPs!


 



Want 10% more hash from your rigs?



We promise to keep your email safe and never spam you.



Copyright (c) 2012-2019 Portable Instant Mining Platform LLC. All rights Reserved.