MonthMarch 2010

remote hard reset a linux server if reboot doesn’t work

Sometimes, reboot or shutdown -r now, don’t work anymore. That really sucks, especially if you have no access to the server room or you just don’t want to get up.

But there might be another solution if you compiled your Kernel with CONFIG_MAGIC_SYSRQ: “sysrq-trigger”. If so, you have the possibility so send some, let’s say binding, commands:

Reset your server (like pressing the hardware reset button):

# echo b > /proc/sysrq-trigger

But, it might be a good idea to sync the hard disks before:

# echo s > /proc/sysrq-trigger

If you like to know more about that, try

One thing that might be worth to point out is how to prevent this behaviour:

doing things with subversion

Because I don’t use subversion that often, i thought that it might be cool to have some basic svn commands written down here… so that’s what i did.

on the server do:

create a new branch:

# svnadmin create /path/to/new/branch
# chown www-data:www-data /path/to/new/branch

the piece of text to put into your apache2 config to enable svn over WebDAV:

<Location /newbranch>
 DAV svn
 SVNPath /path/to/new/branch
 SVNAutoversioning on
 AuthType Basic
 AuthName "Subversion new branch, please authenticate"
 AuthUserFile /path/to/new/branch/.passwd
 Require valid-user

create that .passwd file:

# htpasswd -cs /path/to/new/branch/.passwd username

to add an other user, use only “-c” the second time.

on client side do:

download all that stuff witch is in the repository (checkout):

$ svn co --username username

then, edit stuff. If you added some new files, add them to the repo with:

$ svn add newfile.txt

next time you edit stuff in your local repository, make an update to be sure that you work with up to date files:

$ svn up

and finally, when you are finished working, commit your work back to the repository:

$ svn ci -m 'comment about your changes'

thats it.

If you like to get an actual pro, try this online book: or visit

© 2017 netmess

Theme by Anders NorenUp ↑