Open Tech Notes

“ip route” causes problem

After I re setup the server, there are two weird things happened.

1) I use SSH remotely access the server, after I input the password, it took me about 20 seconds to login in.
2) some clients complained that they could not access the website whereas others could.

After dinner, I came across my friend’s home, in his computer, the website could not be accessible.

Then, I was thinking … he used different ISP, the ip address in his computer starts with 64 whereas mine starts with 24.

I login the server again and type "ip route" and found there was an entry forward all ip start with 64 to one special ip address.(who set this?)

After I deleted this ip route, the two problems above are gone!

Two hard drives failed at the same time on RAID5

Obviously, it is a huge disaster, 2 out of 3 hard drives failed in RAID5 coincidently at the same time. Fortunately, I have the backup, but still, it is painful to recovery every details.

12:Option expected

This is the only error message I encountered on setting up SVN sever on Windows 2003.

Here is the config file:

### This file controls the configuration of the svnserve daemon, if you
### use it to allow access to this repository. (If you only allow
### access through http: and/or file: URLs, then this file is
### irrelevant.)

### Visit http://subversion.tigris.org/ for more information.

[general]
### These options control access to the repository for unauthenticated
### and authenticated users. Valid values are "write", "read",
### and "none". The sample settings below are the defaults.
 anon-access=read
 auth-access=write
### The password-db option controls the location of the password
### database file. Unless you specify a path starting with a /,
### the file’s location is relative to the conf directory.
### Uncomment the line below to use the default password file.
 password-db=passwd
### The authz-db option controls the location of the authorization
### rules for path-based access control. Unless you specify a path
### starting with a /, the file’s location is relative to the conf
### directory. If you don’t specify an authz-db, no path-based access
### control is done.
### Uncomment the line below to use the default authorization file.
# authz-db = authz
### This option specifies the authentication realm of the repository.
### If two repositories have the same authentication realm, they should
### have the same password database, and vice versa. The default realm
### is repository’s uuid.
# realm = My First Repository

———————-

Solution is very simple, just remove the SPACE in front of lines which are not be commented.