| Time |
Nickname |
Message |
|
01:41
🔗
|
phillipsj |
hmm, maybe GLaDOS is not a bot... |
|
07:36
🔗
|
GLaDOS |
..I'm not a bot, no. |
|
08:05
🔗
|
ersi |
that's what all the bots say |
|
08:27
🔗
|
GLaDOS |
I swear! |
|
08:28
🔗
|
ersi |
No swearing! Bad bot, bad! |
|
08:28
🔗
|
* |
ersi smacks GLaBOT |
|
08:28
🔗
|
ersi |
^w^ |
|
08:28
🔗
|
GLaDOS |
:c |
|
13:06
🔗
|
BiggieJon |
how do I stop tinyback if I'm running outside the warrior ? |
|
13:09
🔗
|
phillipsj |
In practice, I have not seen bots bothering to deny that they are bots. |
|
13:12
🔗
|
phillipsj |
if tinyback is the name of the process, run 'ps -A | grep tinyback' then kill <pid> |
|
13:15
🔗
|
ersi |
The answer is to `touch STOP` if you're using run-pipeline outside of the warrior |
|
13:15
🔗
|
ersi |
do that in the working directory, where you started it from |
|
13:27
🔗
|
Cameron_D |
what if I'm just doing ./run.py? |
|
13:32
🔗
|
ersi |
Then go with phillipsj's line |
|
23:32
🔗
|
aMunster |
i've got one machine happily receiving tasks, but my second is getting told there are no tasks available |