Home / user-1909

staticsan's questions

Martin Hope
staticsan
Asked: 2010-10-20 19:10:26 +0800 CST
  • 26

I'm developing a web-based Java application at work and (obviously) have to run it locally during development. I've figured out the Tomcat docs and have a suitable context.xml file in /etc/tomcat6/Catalina/localhost/ but every so often, Tomcat decides to delete it! Which means I have to put it back and restart Tomcat.

Why does it do this? I have searched the Tomcat docs about it and am none the wiser.

(Oh yes: it's not actually called context.xml but owners.xml as that's the HTTP path prefix for this application.)

Update

I've now seen Tomcat delete the file whilst Tomcat was running. I think I need to file a bug...

tomcat
Martin Hope
staticsan
Asked: 2009-09-04 22:23:11 +0800 CST
  • 3

There are a couple of defaults in the standard Linux shell, bash, that I think need some history brought out. This question is about the prompt.

The default prompt in bash in many Linux distros is [\u@\h \W]\$

For those who can't parse that, it looks like this for a typical user:

[staticsan@walcen files]$ _

The biggest problem with this is that it only tells you the name of the current directory. "files" could just as easily be /var/www/files/ as /home/staticsan/files (and that's a simple example). A full path makes more sense, so I have to change it every time I setup a new box or create a new user.

So why is the default set to what it is?

linux bash prompt
Martin Hope
staticsan
Asked: 2009-08-28 23:07:29 +0800 CST
  • 0

I have a problem with an end-user who can't connect to their MySQL Server.

The facts:

  • Client is Windows XP on a corporate Domain. Group policy has disabled Windows Firewall and there is no other firewalling software installed.
  • The software MySQL's own query browser, v1.1.20, and is a permitted install.
  • The username and password are correct.
  • The query browser takes longer than a normal connect when trying then returns the error message "MySQL Error Number 2003 - Can't connect to MySQL Server on 'hostname' (10060)"
  • The query browser can "ping" the server with no problem.
  • Manually connecting using Window's own telnet command succeeds and the handshake initiation is clearly visible. So the hostname resolves on that PC and there is no networking issue (e.g. routing).
  • We've tried re-installing the query browser to no avail.
  • The server is running fine and everyone else who needs to connect (including myself) can successfully connect, most of them using the exact same version. So it is not a server problem.

Googling the error shows this is a classic unavailable connection problem and lots of links show fixes for the server, but the problem seems to reside entirely in the install of the query browser, which doesn't make any sense. Thus Google is no help.

Has anyone else seen this or can offer suggestions?

windows