[Afronanny]

Why am I getting this message when trying to use nemrun? I've been using it fine for months, but this started showing up yesterday and I've made no changes to the script.

ERROR: List of process IDs must follow -p.
********* simple selection *********  ********* selection by list *********
-A all processes                      -C by command name
-N negate selection                   -G by real group ID (supports names)
-a all w/ tty except session leaders  -U by real user ID (supports names)
-d all except session leaders         -g by session OR by effective group name
-e all processes                      -p by process ID
T  all processes on this terminal     -s processes in the sessions given
a  all w/ tty, including other users  -t by tty
g  OBSOLETE -- DO NOT USE             -u by effective user ID (supports names)
r  only running processes             U  processes for specified users
x  processes w/o controlling ttys     t  by tty
*********** output format **********  *********** long options ***********
-o,o user-defined  -f full            --Group --User --pid --cols --ppid
-j,j job control   s  signal          --group --user --sid --rows --info
-O,O preloaded -o  v  virtual memory  --cumulative --format --deselect
-l,l long          u  user-oriented   --sort --tty --forest --version
-F   extra full    X  registers       --heading --no-heading --context
                    ********* misc options *********
-V,V  show version      L  list format codes  f  ASCII art forest
-m,m,-L,-T,H  threads   S  children in sum    -y change -l format
-M,Z  security data     c  true command name  -c scheduling class
-w,w  wide output       n  numeric WCHAN,UID  -H process hierarchy

[Nephyrin]

I just randomly found this thread googling nemrun, but it's worth noting that this was a bug fixed in nemrun 1.6, in case others are finding this googling said issue.

(it was doing something like "ps -p `cat update.lock`", and if update.lock got corrupted (no Pid inside) ps would explode)

[meecrob]

Thank you Nephyrin.

[moxie2020]

Originally Posted by Nephyrin I just randomly found this thread googling nemrun, but it's worth noting that this was a bug fixed in nemrun 1.6, in case others are finding this googling said issue. (it was doing something like "ps -p `cat update.lock`", and if update.lock got corrupted (no Pid inside) ps would explode)

Nephryin, Little Help Please...

I am trying to use nemrun but I am having trouble with the updater. It doesn't seem to be detecting the updates. I just see it continually looping 45 minutes after the update was released.


[Fri Jul 20 194:04 EDT 2012] :: Checking for updates
[Fri Jul 20 194:04 EDT 2012] :: Running srcupdatecheck
[Fri Jul 20 194:04 EDT 2012] :: Up to date!
[Fri Jul 20 194:04 EDT 2012] :: Freeing update lock
[Fri Jul 20 194:04 EDT 2012] :: Update check complete
[Fri Jul 20 194:04 EDT 2012] :: Update daemon mode. Waiting a few seconds and checking again!


I am using the latest versions from your site.