How to restart ES from a script?

[meleu]

@TMNTturtlguy I've recently realized that pkill accepts regex. Then here is my suggestion:

touch /tmp/es-restart && pkill -f "/opt/retropie/supplementary.*emulationstation([^.]|$)"

OK, maybe Regular Expressions is a not-very-human-readable thing, but it's really worth learning. ;-)

[cyperghost]

Attentention @meleu that kills 2 of 3 processes in my configuration!
That's a nice one liner ... what happens if the creataed es-restart will reside?

[TMNTturtlguy]

@cyperghost @meleu So first off, @cyperghost script appeard to work a few times in my testing. Then i tried @meleu one liner. This did not work. It gave me weird lines of code across the screen and then It exited me to a black screen and i had to go into putty and sudo reboot.

I then went back to @cyperghost script. Now the first time I run my change script it changes my es_systems and successfully restarts. However, the second time i go into the script, the script goes crazy and auto runs a few things and then the weird code that came up with @meleu script ran reappears and i exit to a black screen again.

At first look it appears that @meleu script broke something and now whenever i run a touch /tmp/es-restart command it gets weird. I go into /temp/ folder and es-restart does not exist. @meleu, can i reverse this script somehow so i can go back to test @cyperghost script which appeared to work?

[meleu]

@TMNTturtlguy I'm away from my pi now, will try to post something more robust later. ;-)

[cyperghost]

@TMNTturtlguy Yes I wrote in my last post. @meleu call kills 2 PIDs - mine just one - the latest!

I think we should create a coding section - this can run sometimes into trouble. The configuration of RetroPie can differ much from user to user. In this case we use brutal weapons to terminate ES. That's not good .... and makes user support heavier!

@meleu
Please check if es-restart can be alive!
On every reboot the files are force removed! So I strongly suggest they can run into this habbit. And I just kill one PID - I think that's the SDL windows. But I'm not sure...

[meleu]

@cyperghost said in How to restart ES from a script?:

Attentention @meleu that kills 2 of 3 processes in my configuration!

could you please post here the output of these commands (in this order)?:

pgrep -lf emulationstat

touch /tmp/es-restart && pkill -f "/opt/retropie/supplementary.*emulationstation([^.]|$)"

pgrep -lf emulationstat

[TMNTturtlguy]

@meleu Sounds good, i have to do real work as well. I will be away from my pi all weekend, so we might have to resume this on sunday or monday.

@cyperghost I am 99% sure that your method worked, my only concern was your statement about what happens when we update ES. I want this to work for all users as you just suggested in your latest post. This is why i tried @meleu method as it appeared to more straight forward. Problem is that now i can't run either anymore because for some reason @meleu code might have done something in the background?

[cyperghost]

@TMNTturtlguy No there is no difference in mine or meleus method. Both methods can run into trouble!

[TMNTturtlguy]

@meleu

[meleu]

@TMNTturtlguy hey bro, Linux shell is very rigorous with typing! :)

• use emulationstat not emulastionstat
• use /tmp/ not /temp

[TMNTturtlguy]

@meleu sorry, i am trying to work on work and do this at the same time, i am failing! give me a second

[cyperghost]

@TMNTturtlguy Please don't get me wrong he needed the PID.
Edit: Sorry for that kind of work! I know you just want to help :)

@meleu

868 emulationstatio
874 emulationstatio
877 emulationstatio

That are three PIDs
I kill only 877

output of mine
via echo 
echo $(pgrep -l -n emulationstatio | awk '!/grep/ {printf "%s ",$1}')

results:
877

I kill 877 with
kill 877

after checking again I see 3 PIDs
868
874
1026

your command

I use e param for listing:
pkill -f -e "/opt/retropie/supplementary.*emulationstation([^.]|$)"
emulationstatio killed (pid 874)
emulationstatio killed (pid 877)

after

with:
pgrep -lf emulationstat
nothing

So the whole system is killed!

[TMNTturtlguy]

@meleu

Here is the touch line - this is the same error i get when i run from my script and what happens now when i use @cyperghost script a 2nd time. First, this is what i typed in when retropie was running properly:

And here is the outcome on the pi - no output in putty command line

running pgerp -lf emulationstat now gives no output at all.
when i touch a button on my controller i exit to a black screen on the pi, have to sudo reboot.

[cyperghost]

@TMNTturtlguy Please delete /tmp/es-restart manually
What has OMX-Player to do with Emulationstation?

pleas @TMNTturtlguy
Try this in shell output of ps -a

in shell

echo $(pgrep -l -n emulationstatio | awk '!/grep/ {printf "%s ",$1}')

No worries you can't make mistakes with that. That are all output commands.

[TMNTturtlguy]

@cyperghost that is the thing, i don't have a /tmp/es-restart to delete, it isn't there! I am pretty confused, when i did my attempts running touch es-restart I always got a /tmp/ file. any issues, just sudo rm and it was fixed. Now i don't see a /tmp/es-restart file, however it is retaining the error screen from @meleu script.

As you might be able to tell, i am not a coder, so i am really stretching here creating this stuff. It is fun, but there is a lot I don't understand. Can you provide more info on what you want me to do? Not sure what you mean by :

Try this in shell output of ps -a
in shell
echo $(pgrep -l -n emulationstatio | awk '!/grep/ {printf "%s ",$1}')

[meleu]

@TMNTturtlguy I'll sort it this evening, but when that happens with your terminal try to (maybe blindly) type reset and press enter.

[cyperghost]

@TMNTturtlguy
connect via SSH
in prompt type ps -a
That list all process with tty1 output

then create the file es-restart with sudo command
sudo touch /tmp/es-restart

check existance with
ls /tmp

into the ps list... take the pid from ES with the highst number (that's the latest processes) and type
kill 1234 your PID here should not be 1234 ;)

after that

ps -a
again... What do you see?

[meleu]

@cyperghost maybe ps -a | grep emulationsta can give a cleaner output for him. :)

[cyperghost]

@meleu well that are only 2 or three more processes - clean enough but thank you ;)

@TMNTturtlguy I'm also not a coder - I made my master degree in chemistry

[TMNTturtlguy]

@cyperghost thanks for explaining!

To answer your question from the previous post - OMX is the screensaver running, part of a new update to ES.

here is my output - when i ran the kill line, it killed the screensaver.