> "I schedule my server to restart every-right at 3am local time."
> Is there an easy way to accomplish this? Or is this done with some script?
> Would you mind sharing more details about this?
I have a small /etc/init.d script which does:
start) switch to wiab user
run /home/wiab/start-wave.sh script which is a wrapper around
the run-server.sh script supplied with wave, and checks for any
updates to the jar's I might have pushed to a separate folder on the
server (a quick attempt at remote-deployment)
stop) switch to wiab user
killall java
The killall works because WIAB is the only java app running under that
user. The java apps running under the other users can't be killed with
this method because of the user permissions.
> "Why do you need to be able to access it from both IPs, can the
> external one not be used from inside the network?"
> Yeah, we cant connect to the server with the external ip from within the
> network. The only answer i got from our network guy in the building was "use
> the internal ip.." I tried searching google for ways to do this, but the
> only solutions i could find was tampering about with router settings, which
> i don't have access to.. Any easy solutions or pointers in the right
> direction is much appreciated.
Unfortunately, if your network person says so then that is the end of
the discussion for you, since this is entirely dependent on your
network hardware being clever enough to realise that it can intercept
packets to its own ip outgoing from the lan.
Looking back at the original problem: Does WIAB store the ip used to
upload the file as part of the url (hence causing the issues when you
download)? Since this does seem like a rather strange design feature
(I didn't implement this code). If so, then this shouldn't be too
difficult to fix in the WIAB code. @Yuri,Michael: comments on this
(pointers on where in the code base to look for this? (Since I still
get lost navigating it))
