2014-07-17, 23:10
it turned out to be dead easy to fix! no idea why the package builder would do this but he was hard coding the port into the line that was starting the application. Why would he do that? no idea.
Anyhows I ssh'ed into the NAS ran
vi /var/packages/htpcmanager/scripts/start-stop-status
changed the line
su - ${USER} -c "PATH=${PATH} ${PYTHON} ${HTPCMANAGER} --datadir ${DATA_DIR} --pid ${PID_FILE} --daemon --port 8087"
to
su - ${USER} -c "PATH=${PATH} ${PYTHON} ${HTPCMANAGER} --datadir ${DATA_DIR} --pid ${PID_FILE} --daemon
press ESC and entered :wq to save
From NAS interface stopped the package and restarted and it worked fine.
removing the --port 8087 stopped hard coding the port number and by magic I could change the port in the user interface again and because the package is only updated via a git command it is safe to update whenever I like.
Anyhows I ssh'ed into the NAS ran
vi /var/packages/htpcmanager/scripts/start-stop-status
changed the line
su - ${USER} -c "PATH=${PATH} ${PYTHON} ${HTPCMANAGER} --datadir ${DATA_DIR} --pid ${PID_FILE} --daemon --port 8087"
to
su - ${USER} -c "PATH=${PATH} ${PYTHON} ${HTPCMANAGER} --datadir ${DATA_DIR} --pid ${PID_FILE} --daemon
press ESC and entered :wq to save
From NAS interface stopped the package and restarted and it worked fine.
removing the --port 8087 stopped hard coding the port number and by magic I could change the port in the user interface again and because the package is only updated via a git command it is safe to update whenever I like.