admin how-to

(Difference between revisions)

Jump to: navigation, search
(update ps command to see root/apache proc ownership, use of killall command)
(attack logs)
Line 28: Line 28:
** <code>sudo kill -9 1337</code>
** <code>sudo kill -9 1337</code>
* if there are too many to do individually, you can also use:
* if there are too many to do individually, you can also use:
-
** <code>sudo killall httpd</code>
+
** <code>sudo killall -9 httpd</code>
* re-run the ps command:
* re-run the ps command:
** <code>ps -eaf | grep http</code>
** <code>ps -eaf | grep http</code>
Line 86: Line 86:
=== mailing list archives ===
=== mailing list archives ===
* ...
* ...
-
 
=== shorteners ===
=== shorteners ===
* http://microformats.org/w/hcard should go to http://microformats.org/wiki/hcard
* http://microformats.org/w/hcard should go to http://microformats.org/wiki/hcard
Line 92: Line 91:
=== other ===
=== other ===
 +
* ...
 +
 +
== attack logs ==
 +
Note any logs / summaries of attacks. Anything more than a summary should be moved to its own page.
 +
* 2012-02-01 openlinksw were issue excessive http requests, sufficient to unacceptably increase user access latency. banned an IP.
 +
* 2010-10-31 Banned demo.OpenLinkSW.com by IP, 63.119.36.50 -Rohit
* ...
* ...
== see also ==
== see also ==
* [[admins]]
* [[admins]]

Revision as of 07:17, 2 February 2012


This is a reference for various tasks that admins may have to perform.

Contents

web server restart

If you're reading this then either the server is up, or the server is down and you're reading a Google Cache copy (thus it's still useful to post this here).

If the web server is down, e.g. someone notes on IRC or Twitter:

Then:

server transition testing

Some things to check when transitioning to / setting up a new server.

editing your local hosts file

In order to test a new server from your local machine and still have hardcoded URL references work, you may need to manually edit your local machine's hosts file, per:

http://www.howtogeek.com/howto/27350/beginner-geek-how-to-edit-your-hosts-file/

Your browser should now behave *exactly* as if you'd switched actual DNS.

This makes it a very good way to test.

DNS flush cache tips

If you're using OSX, you'll probably have to run this to flush the local dns cache:

dscacheutil -flushcache

current servers being tested

home and blog

wiki

irc bots

profiles

media

mailing list archives

shorteners

other

attack logs

Note any logs / summaries of attacks. Anything more than a summary should be moved to its own page.

see also

admin how-to was last modified: Wednesday, December 31st, 1969

Views