mbm.sh: 37: [: No: unexpected operator

[shpapy]

Instance config_2_GOOGLE.json! Bot: [botname].
Password:
mbm.sh: 37: [: No: unexpected operator
Screen is running. Lets see if he is actually working.
cat: /var/log/screenlog/shpapy.log: No such file or directory
date: invalid date ‘+%s’
mbm.sh: 54: mbm.sh: arithmetic expression: expecting primary: " 1469751120 - "

[prmths-codes]

We are working on an install script right now that puts all things together for the startup.

Im going to update the readme meanwhile soon about the ToDo before start.

[shpapy]

Great stuff, let me know and i will test it.
10x.

[prmths-codes]

I added the necessary parts to the wiki and added an install.sh to add and fill the logs.
Check it out please.

[shpapy]

hi, dosen't work

install.sh: 6: install.sh: /home/shpapy/mbm: Permission denied
mkdir: missing operand
Try 'mkdir --help' for more information.
chmod: missing operand after ‘777’
Try 'chmod --help' for more information.
grep: /config_*: No such file or directory

shpapy@puppy:~/mbm$ sudo sh mbm.sh
chown: missing operand
Try 'chown --help' for more information.
find: `/config_*': No such file or directory

Boss, we have 0 Bots playing around here.
Lets see if these splashers are doing their fucking jobs.

---

Instance config_01_PTC.json! Bot: yabaddddoooo.
He isnt running at all???! He aborted with:
tail: cannot open ‘/yabaddddoooo.log’ for reading: No such file or directory

Started.

mbm.sh: 47: mbm.sh: cannot create : Directory nonexistent

Instance config_02.GOOGLE.json! Bot: shpapy.
He isnt running at all???! He aborted with:
tail: cannot open ‘/shpapy.log’ for reading: No such file or directory

Started.

mbm.sh: 47: mbm.sh: cannot create : Directory nonexistent

Instance config_2_GOOGLE.json! Bot: shpapy.
He isnt running at all???! He aborted with:
tail: cannot open ‘/shpapy.log’ for reading: No such file or directory

Started.

mbm.sh: 47: mbm.sh: cannot create : Directory nonexistent

Instance config_2_PTC.json! Bot: yabaddddoooo.
He isnt running at all???! He aborted with:
tail: cannot open ‘/yabaddddoooo.log’ for reading: No such file or directory

Started.

mbm.sh: 47: mbm.sh: cannot create : Directory nonexistent

Summary:

OK: 0 / 0 Bots
Sick: 0 / 0 Bots
Didnt run: 4 / 0 Bots

[shpapy]

same same with new code

[shpapy]

the issue is the declaration of the variables
when i add
WDIR=/home/shpapy/PokemonGo-Bot # Most important directory: The PokemonGo-Bot install dir
CDIR=$WDIR/configs # Where your configs are
LDIR=/var/log/screenlog # Whats your desired log dir, should be chmod 777
LOG=$LDIR/mbm.log # In the log dir, how should the mbm log be called
LINES=200 # For the checkups, how many lines you want to check? DONT CHANGE
SECONDS=300 # Whats the delta range? Its the last entry distance in the log. DONT CHANGE
WUSR=shpapy # With what user you want to start the screen sessions? root is unwise and unsafe...

into the scripts its fine

[prmths-codes]

Pull the master again. We made alot of changes lately. Should be fine with

bash mbm.sh

[prmths-codes]

Issue with the variables was, that when you call the script with sh they are called with . /$PATH.
And when via bash or ./ its called with source $PATH.

We changed it to bash now.

[shpapy]

it looks much better now

1. i changed the source /home/shpapy/mbm/config to represent the real location (it was pointitng to the dir not to conf itself)
2. it looks better now see below error

mbm.sh: line 77: kill: Sockets: arguments must be process or job IDs
mbm.sh: line 77: kill: in: arguments must be process or job IDs
mbm.sh: line 77: kill: /var/run/screen/S-shpapy: arguments must be process or job IDs

Restarted.

[prmths-codes]

The new kill function is contributed by viruz82.
I hope he can find out whats wrong there.

Glad its running good on your end :)

[shpapy]

MInor adjustments but it's good stuff
I would switch to tmux and open multiple windows per bot
Weekend is coming so I got time to fork and play. :-)

Thanks,
Marius

On Jul 29, 2016 17:50, "Jakob" notifications@github.com wrote:

The new kill function is contributed by viruz82.
I hope he can find out whats wrong there.

Glad its running good on your end :)

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#1 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEwbH0xU5msG-e0OmXbn2v3iyxzRb6G3ks5qaiFDgaJpZM4JXw2S
.