A glass case of thoughts » Linux

What to do : When your SVN client saves a wrong password -> Make it forget it

Jyotsna — Wed, 13 May 2009 06:30:58 +0000

Applies to:
Any SVN client using putty to connect to SVN server. For e.g. tortoise SVN

Who is this post for?
This post is for anyone who wants SVN client and server to forget currently configured password

Steps to follow

Know your repository URL
For this you should be using tortoise SVN repo-browser and check out the URL. In my case, it looks like
```
svn+ssh://jyotsnas@visharad/svnRepos/travel_broker
```
This tells me following
- linux username being used is jyotsnas
- the svn server is named as visharad
- Probably all SVN repositories are located under /var/svnRepos
Now that we know the servername, in this case ‘visharad’, open putty. Under saved sessions list, you should find your server name. Refer to following screenshot for the same

visharad in saved sessions of putty
Click on Load button so that we can find out more. Putty looks like following when I clicked Load

visharad session loaded in putty

Looking at this I have more concrete information about server i.e. Host name/IP : 192.168.1.50
Let’s move to the SSH->Auth in left tree structure –

visharad ssh auth settings in putty

This screen tells me a path to a private key file on my machine.
```
F:\Jyotsna\SVN sessions\visharad.ppk
```
Delete this path from the text box.
Go back to sessions in left tree and click on save.

When you delete this path, putty is going to forget the password to be used. Since tortoise SVN uses putty in turn to connect to server, it will forget it too. And that is it.

Questions you might have

Why should I not delete the session instead of the private key file path?

In cases like mine, visharad name was given to a machine with IP 192.168.1.50. If I had deleted the session, I would have have to relocate all the SVN repositories already checked out on my machine so that the new URL contains 192.168.1.50 instead of visharad. Not deleting the session saves this hassel of mine and still make tortoise svn not use the remembered password.
How can I make tortoise SVN remember a new password?
Just refer to this link for the instructions

Related posts

linux: handy commands

Jyotsna — Wed, 18 Mar 2009 06:10:08 +0000

copy files from one linux server to another through shell

$ scp user@from_computer:dir/filename user@to_computer:dir/filename

open shell to another linux machine from one through shell
```
$ ssh user@to_computer
```
Prints the owner of every file or directory in the current directory. The AWK syntax is simply “print the 3rd field in every line of data”
```
ls -l | awk '{print $3}'
```
To get the owner of only one file (filename):
```
ls -l | grep filename | awk '{print $3}'
```
To compress a folder:
```
zip -r target.zip folder/
```
User creation
```
useradd username
```
Change user password
```
passwd username
```
Add user to a group
```
usermod -g grpname username
```

Import SQL script to an empty mysql database

mysql -u root -p database_name < script_file.sql

Unfreeze vi editor in terminal window when frozen because of ctrl+S action
```
press ctrl+q
```
Reboot linux server remotely
```
sudo reboot
```
Shut down linux server remotely
```
sudo shutdown -h now
```

Kill a process

top
type k to kill a process. You will be prompted for the PID of the task, and the signal to send to it. For a normal kill, send signal 15. For a sure, but rather abrupt, kill, send signal 9. The default signal, as with kill(1), is 15, SIGTERM. This command is not available in secure mode.

To close port – 80 in following example
```
fuser -k 80/tcp
```

linux how to: replicate svn repository

Jyotsna — Sat, 28 Feb 2009 11:27:22 +0000

Task at hand:

I have a repository on one of the linux server. As a part of upgradation process, we decided to move the SVN server to a newer better linux infrastructure. Task at hand is to replicate the svn repositories on new server.

Solution:

Create dump for existing repository
```
svnadmin dump /path/to/repo > /path/to/dump/folder/myrepo.dump
```
This command creates a .dump file and shows the revisions being dumped as it progresses
Transfer the dump file to new server. This can be accomplished through SSH / FTP connection or a simple scp command as:

scp /path/to/dump/folder/myrepo.dump user@new_server:/path/to/dump/folder/myrepo.dump

Log into new server and switch to the directory where you want to place your replicated svn repository. Then, create an empty svn repository
```
svnadmin create myrepo
```

Load empty reposity with dump file

svnadmin load myrepo < /path/to/dump/folder/myrepo.dump

Define group ownership and permission

chown -R :all myrepo
chmod -R 770 myrepo

Related posts

IIS SSL and linux openSSL

Jyotsna — Mon, 19 Jan 2009 12:02:36 +0000

I have a .NET web service that I want to be accessed over https rather than http. Problem is HOW !!

Solution:

Activate SSL on web server (IIS)
- Follow steps 1 through 4 of this very useful blog by Eric Longman
Specify the file for which SSL is required
- Through inetmgr, browse to the file (in my case the .asmx file). Right click -> Properties -> File Security -> Secure Communications -> Edit
- Check Require SSL Channel (SSL)

And you should be done.

Related useful article:
CONSUMING WEBSERVICES OVER HTTPS (SSL)

linux: create svn repository

Jyotsna — Fri, 26 Dec 2008 06:38:57 +0000

Assumptions:
You already have SVN installed on your linux server. If you do not know if it is installed, just type command

which svn

If this returns a valid path as output, then it means that svn is installed on your linux box. If not, you need to install it. Installing subversion is very easy (for most distributions) and ample documentation is available on the web. You can start with http://subversion.apache.org/.

Four steps to complete svn repository creation on linux

log onto server as root
I prefer to have all svn repositories in one directory for better organization and easy maintenance. So next step for me would be to change to my svn directory.
```
cd /svnRepos
```
If you do not already have a directory for svn repositories, I would recommend creating one.
```
mkdir svnRepos
```
Create repository using following command

svnadmin create /path/to/repo/RepoName

where : RepoName is the name of repository to be created. As an example, I want to create a repository for my testproject. I would write

svnadmin create testproject

Change group ownership of repository for the intended group. In this case, consider I have a user group created as “all” and I want this group to have ownership to this repository.
```
chown -R :all /path/to/repo/RepoName
```
Grant Read/Write/Execute permissions to “all” on this repository
```
chmod -R 770 /path/to/repo/RepoName
```

After this, all you need to do is

Install a client like tortoiseSVN on the user’s machine
SVN Checkout the repository. I would use a URL like following to connect to my newly created repository
```
svn+ssh://username@servername/path/to/repo/RepoName
```
Where
- username: one of the users from group all
- servername: my linux server which hosts SVN
For my testproject, the path looks like
```
svn+ssh://jyotsnas@servername/svnRepos/testproject
```

Related posts