View Single Post
  #1  
Old 12-09-2014, 09:31 AM
vsab's Avatar
vsab
Discordant
 
Join Date: Apr 2014
Location: United Kingdom
Posts: 276
Default suppressing db_update on Linux (Debian 7)

I mentioned this on IRC, but I rarely get to go on IRC and due to time differences had to go before I got a reply. And also, it's worth having any answer documented for others who may have the same issue.

Currently what is happening is that even after I run ./world manually and update the db, the script continues to run when I use my normal startup script (which runs ./world > /dev/null 2>&1 &)

I tried this: http://wiki.eqemulator.org/i?M=Pastebin&Paste=xRJzfmq2
by uncommenting
Code:
#./world 2>&1 > logs/world &
and conmmenting out
Code:
./persist_world
as I'm guessing ./persist_world is a custom script I don't have, however this still runs the .pl file, which ends up using 100% CPU and spamming logs.

What I would like to do is adapt this:-
http://wiki.eqemulator.org/i?M=Pastebin&Paste=tiC4AqP8

Such that the db_update.pl file is either not called, or is automatically passed the "0" to exit.

One thing I did notice- it did seem to re-download the script every time- so perhaps I have a file system permission issue?

99% of the time I run world it would not be after recompiling/updating the source, so I'm quite happy to have to "opt in".
Reply With Quote