You could always write your own script and have pwAdmin call it instead of whatever it does .. ?? .. ??
Well thank you for invoking/inducing my insomnia (no JK it's really not your fault) but, I went to do a lil testing and even 136 isn't working for me RN
So, knowing full well that too once worked, I wonder if it isn't something (somehow) related to newer version of Ubuntu? That doesn't even make sense even to myself RN but then again I am sleep deprived at this point >.>
well in the meantime, for manual or scripting use you could use something like the following to stop authd:
kill -9 $(ps aux | grep "./authd" | grep -v grep | awk '{print $2}')
same exact thing/concept for maps
kill -9 $(ps aux | grep "./gs is02" | grep -v grep | awk '{print $2}')
where obviously is02 equals the instance you want stopped
That's how I "manually" stop stuff
You could get even a little fancier and "borrow" this, this is a small script I just tossed together that literally stops either ALL maps, OR any single specified map (one at a time):
Code:#!/bin/sh case "$1" in *s**) kill -9 $(ps aux | grep -v grep | grep "[.]/gs $1" | awk '{print $2}') ;; *) clear echo "" echo "Would you like to stop ALL maps?" echo "y/N" echo "" read -s -n 1 confirmall case $confirmall in n|N) clear echo "" echo "NO maps were stopped..!" echo "" ;; y|Y) kill -9 $(ps aux | grep -v grep | grep "[.]/gs $1" | awk '{print $2}') clear echo "" echo "ALL maps have been stopped..!" echo "" exit 1 esac exit 0 exit 1 esac exit 0
Oh and I even threw in the "failsafe"
that is, it "checks" if you actually WANNA stop ALL maps if you just run the script with no "command line arguments"... Then you have to hit either Y or N to stop ALL
otherwise you could run like ./script is02
and it would stop ONLY is02
also, more specifically to you, I know you may be skeptical of getting her on a terminal already, and I would agree with probably not trying to overload her with having to actually manually do so much (ps aux grep kill pkill n all this poop may be a bit of an overload)... But I would think if you tossed that script together, that could be a great way to start learning terminal; by running scripts you've made (or borrowed)...
Then you know that's going to lead to "how to make scripts"!
But yea, kids minds are sponges - the earlier the better!!!
But I would think that may work out for you two as well, just tell her "ok, if you want/need to stop a map you type './stopmap is##' to stop that map": (and ofc there's nothing wrong with using pwAdmin to get the numbers/list!) And like I said ./script (presumably something like stopmap or stopmap.sh [I'd personally actually just go with stopmap]) ran without something like <script> is02 - will presume to kill all maps, BUT ask/confirm FIRST!
LMK
I would also think, you could even modify pwAdmin to "call" this instead of whatever method it is currently using !
at this point I am trying to think about if/how I'm going to handle this for the release because, this could be ALL versions, and rebuilding ALL versions is going to give me a migraine - IF I even actually get the time to do it any time soon
Oh and just in case you didn't know, you could also put a script like that in /usr/local/bin
Then you can skip the preceding ./ when launching it, AND it can be run from anywhere (while in any directory)...!
thanks for the script , it would be a great help
i actually did just that, less fancy though.
for the march release 2021 making her power on the machine letting it boot then her going to a browser starting the pw server letting her choose maps
for v1.5.5 its is61 and is69
for stopping a map, i tell her to go to the terminal and type in pkill -f ' is## '
## = map number as listed on the pwadmin site
then hit refresh on the browser to confirm the map stopped
then for stopping the server i let her click on stop in pwadmin then for audth same command inside terminal
pkill -f ' authd '
hitting refresh again for stopage confirmation
doing this she could restart the server and or just restart or choose other maps again in pwadmin without running out of ram
i told her dont worry about messing anything up at first, the server is there play with it
thanks for the tips, im still trying and looking into all the server versions in mar 2021 release and compare to an older release
" I would also think, you could even modify pwAdmin to "call" this instead of whatever method it is currently using !- - - Updated - - -at this point I am trying to think about if/how I'm going to handle this for the release because, this could be ALL versions, and rebuilding ALL versions is going to give me a migraine - IF I even actually get the time to do it any time soon "
that might be a good solution not diving into everything again and just modify the "call" if everyone would not find something else, not rebuilding the whole release. coz the pkill works and the authd and maps responds to shutting down manually and turning back on via pwadmin maybe patch server side or a small update file
.. about the newer version of ubuntu, as cause the 2014 release used 12.04.3 but just up to v1.5.1 if i remember correctly. i doubt its ubuntu might be just whats inside .jsp or the dated code but ive tried using older browsers on win xp (ie 6 - 11, chrome, firefox)and windows 7 for the pwadmin march 2021 release, same result just letting you know about my experiments.
i edited something to my pwadmin .jsp files i just cant post it atm according to forum rules
which stopped all servers including authd within pwadmin replcing -9 switch to -f in pkill
Last edited:
