- # windows7 magical mystery tour lets us create a file c:\\tmp_pids.txt, but then it's not really there
- # in the root of drive c: when we look for it later. hoping to fix that problem by using a subdir, which
- # also might be magical thinking from windows perspective.
+ # windows7 magical mystery tour lets us create a file c:\\tmp_pids.txt, but then it's not
+ # really there in the root of drive c: when we look for it later. hoping to fix that
+ # problem by using a subdir, which also might be magical thinking from windows perspective.
- # we have abandoned all hope of relying on ps on windows. instead
- # we use wmic to get full command lines for processes.
- # this does not exist on windows home edition. we are hosed if that's
- # what they insist on testing on.
+ # we have abandoned all hope of relying on ps on windows. instead we use wmic to get full
+ # command lines for processes.
wmic /locale:ms_409 PROCESS get processid,commandline </dev/null >"$tmppid"
local flag='/c'
if [ ! -z "$(uname -a | grep "^MING" )" ]; then
wmic /locale:ms_409 PROCESS get processid,commandline </dev/null >"$tmppid"
local flag='/c'
if [ ! -z "$(uname -a | grep "^MING" )" ]; then
- local CR='
-' # embedded carriage return.
- local appropriate_pattern="s/^.* *\([0-9][0-9]*\)[ $CR]*\$/\1/p"
- local -a PIDS_SOUGHT
+# local CR='
+#' # embedded carriage return.
+# local appropriate_pattern="s/^.* *\([0-9][0-9]*\)[ $CR]*\$/\1/p"
+ local appropriate_pattern="s/^.* *\([0-9][0-9]*\) *\$/\1/p"
# remove the first line of the file, search for the pattern the
# user wants to find, and just pluck the process ids out of the
# results.
# remove the first line of the file, search for the pattern the
# user wants to find, and just pluck the process ids out of the
# results.
- if [ ${#PIDS_SOUGHT[*]} -ne 0 ]; then echo ${PIDS_SOUGHT[*]}; fi
+ if [ ${#PIDS_SOUGHT[*]} -ne 0 ]; then
+ local PIDS_SOUGHT2=$(printf -- '%s\n' ${PIDS_SOUGHT[@]} | sort | uniq)
+ PIDS_SOUGHT=()
+ PIDS_SOUGHT=${PIDS_SOUGHT2[*]}
+ echo ${PIDS_SOUGHT[*]}
+ fi