Quote from: damNmad on August 29, 2017, 02:14:08 PM

Quote from: helpme85 on August 29, 2017, 01:06:14 PM

Quote from: papampi on August 29, 2017, 11:55:20 AM

Is it normal that every time upPASTE reload config it start a new instance of 1bash ?

Code:

m1@m1-desktop-102:~$ ps aux | grep 1bash
m1 2201 0.0 0.0 13320 3876 pts/16 S+ 11:43 0:00 bash /home/m1/1bash
m1 4482 0.0 0.0 13328 3840 pts/23 S+ 12:14 0:00 bash /home/m1/1bash
m1 18432 0.0 0.0 13328 3836 pts/24 S+ 16:18 0:00 bash /home/m1/1bash

Code:

m1@m1-desktop-101:~$ ps aux | grep 1bash
m1 13545 0.0 0.0 13324 3888 pts/17 S+ 16:23 0:00 bash /home/m1/1bash
m1 13546 0.0 0.0 13332 3820 pts/23 S+ 16:23 0:00 bash /home/m1/1bash
m1 13547 0.0 0.0 13328 3892 pts/21 S+ 16:23 0:00 bash /home/m1/1bash

Problem is some times it create multiple miners :

Code:

m1@m1-desktop-101:~$ screen -r miner
There are several suitable screens on:
14358.miner (08/29/17 16:23:44) (Detached)
14348.miner (08/29/17 16:23:44) (Detached)
Type "screen [-d] -r [pid.]tty.host" to resume one of them.

and multiple temp too

Code:

m1@m1-desktop-101:~$ screen -r temp
There are several suitable screens on:
13837.temp (08/29/17 16:23:36) (Detached)
13830.temp (08/29/17 16:23:36) (Detached)
13823.temp (08/29/17 16:23:36) (Detached)
Type "screen [-d] -r [pid.]tty.host" to resume one of them.

The multiple miners only happens on one of my rigs, the other one dont have this issue.
Both has multiple 1bash running but one make multiple miners.

Sorry if I misunderstand.
In v19 you need to run 3main instead of 1bash or run 2unix to refresh the whole

no you don't, you just run 1bash as normal, 1bash has been split into 2 parts (1bash and 3main), where 1bash is a config file and 3main holds all the back end (for people who are not interested in editing it)

At v19 1bash is only a configuration file, there is absolutely no command to run the application in it: D