jaeger420 11 Posted October 19, 2015 My server does not write a PID file when starting up with the following parameters: ./arma3server -config=server.cfg -pid=arma3server.pid It's running ArmA 3 1.52 on the latest Ubuntu dist and, otherwise, runs fine. There are no obvious clues in the log but I can post one, if needed. I've double-checked file permissions and tried different paths but the PID file is never created. Has anyone else experienced this issue? Any suggestions on troubleshooting? Should I take this to the bug tracker? Thanks in advance. Share this post Link to post Share on other sites
Earl Hickey 10 Posted February 2, 2016 Yea, this is still a thing. I use a delayed function within watchdog to grab it. nohup </dev/null >/dev/null $0 pidfetch & echo `date +%s` >${STIMEFILE} ${SERVER} >>${LOGFILE} 2>&1 -config=${CONFIG} -cfg=${CFG} -port=${PORT} -name=${NAME} -pid=${PIDFILE} -servermod=${SERVERMODS} -bepath=${BEPATH} ${OTHERPARAMS} pidfetch) sleep 15s echo `pgrep ${SERVEREXE}` >${PIDFILE} ;; Share this post Link to post Share on other sites