Linux server discussion

LOL..thanks vibro..<G>

on lighter note my server is back up and running..and i got a couple of upgrades for my trouble. dual p-3 1.4's(instead of 1.2's) 2 gigs of ram(from one gig) and 4x36 gig 15k u360 drives instead of 2x74 gig 10k u360's. Nice little speed bumps..<G> Been having fun with the new hdd's..<G>
 
Hescominsoon said:
LOL..thanks vibro..<G>

on lighter note my server is back up and running..and i got a couple of upgrades for my trouble. dual p-3 1.4's(instead of 1.2's) 2 gigs of ram(from one gig) and 4x36 gig 15k u360 drives instead of 2x74 gig 10k u360's. Nice little speed bumps..<G> Been having fun with the new hdd's..<G>
Click to expand...

lol, What in the world would you need that much hd capacity for?
 
I guess I am a disk space control freak. I don't host any clients besides family so I have more control :P

I am so glad to be rid of apache, I don't think I will ever look back to that outmoded thing.

rdiff-backup is pretty nifty, it works over ssh pretty well so you don't need to setup any other services other then having another machine with ssh (and rdiff-backup). It uses rsync to make incremental backups, beautiful and with low overheard (<5% CPU on each machine).

this is the command I run to backup nightly:
# rdiff-backup --exclude /tmp --exclude /var/tmp --exclude /mnt --exclude /proc --exclude /sys / username@hostname::/share/backups/zyria
 
Last edited:
The biggest problem i have seen with apache is the preform mode. I actually force apache to worker mode(which is multi-threaded instead of multi-process). While this might cause issues with older non thread safe scripts..i'm not worried about that..just tuning the system now for max performance consistent with security later..:)
 
Hescominsoon said:
The biggest problem i have seen with apache is the preform mode. I actually force apache to worker mode(which is multi-threaded instead of multi-process). While this might cause issues with older non thread safe scripts..i'm not worried about that..just tuning the system now for max performance consistent with security later..:)
Click to expand...

lighttpd handles request either by using sendfile() or by throwing it off to cgi or fastcgi workers. The main limiting factor is the number of file descripters (100 something by default but you can increase it) and the ability of the fastcgi processes to handle requests or the memory for cgi (which scales poorly). Most of the time lighttpd doesn't even show any CPU usage because it offloads the transaction onto the kernel or the associated interpreter.

The configuration file is beautiful also, it is basically a LUA script and has capacity for logic (ie per domain or socket configuration) beyond what apache is capable of.
 
It is rather sad to see all the people running automated attack systems...

VPS, it has 6 IPs mapped to it so it gets hit like mad. The /var/log/secure is rather funny if you look at it, all the dropped connections.
Code: 
2007-12-01 07:52:30,139 - denyhosts   : INFO     new denied hosts: ['125.64.11.15']
2007-12-02 21:12:14,027 - denyhosts   : INFO     new denied hosts: ['58.61.147.51']
2007-12-03 00:16:15,005 - denyhosts   : INFO     new denied hosts: ['89.149.214.219']
2007-12-03 02:16:14,703 - denyhosts   : INFO     new denied hosts: ['202.111.154.228']
2007-12-04 04:21:35,906 - denyhosts   : INFO     new denied hosts: ['74.94.201.22']
2007-12-04 07:00:06,354 - denyhosts   : INFO     new denied hosts: ['69.60.121.63']
2007-12-04 13:00:04,780 - denyhosts   : INFO     new denied hosts: ['60.12.166.162']
2007-12-04 20:17:04,190 - denyhosts   : INFO     new denied hosts: ['82.100.16.159']
2007-12-05 05:53:36,635 - denyhosts   : INFO     new denied hosts: ['201.219.45.28']
2007-12-06 03:52:40,285 - denyhosts   : INFO     new denied hosts: ['202.29.62.17']
2007-12-08 10:53:56,853 - denyhosts   : INFO     new denied hosts: ['218.97.242.2']
2007-12-09 06:19:56,965 - denyhosts   : INFO     new denied hosts: ['88.37.112.138']
2007-12-09 13:58:27,022 - denyhosts   : INFO     new denied hosts: ['72.229.186.97']
2007-12-09 18:46:22,315 - denyhosts   : INFO     new denied hosts: ['64.251.14.135']
2007-12-09 23:52:25,713 - denyhosts   : INFO     new denied hosts: ['61.19.219.32']
2007-12-10 15:03:26,352 - denyhosts   : INFO     new denied hosts: ['189.21.198.99']
2007-12-11 04:59:27,906 - denyhosts   : INFO     new denied hosts: ['222.73.204.162']
2007-12-11 23:58:34,981 - denyhosts   : INFO     new denied hosts: ['60.191.220.143']

My desktop with only ssh forwarded, opened recently for the new backup system.
Code: 
2007-12-09 06:48:22,447 - denyhosts   : INFO     new denied hosts: ['61.218.44.69']
2007-12-09 08:12:22,492 - denyhosts   : INFO     new denied hosts: ['201.134.248.146']
2007-12-10 20:30:53,154 - denyhosts   : INFO     new denied hosts: ['218.22.25.10']
2007-12-11 02:04:23,645 - denyhosts   : INFO     new denied hosts: ['211.169.249.241']
2007-12-11 17:27:33,272 - denyhosts   : INFO     new denied hosts: ['190.76.248.24']

I wonder if it would be worthwhile to reverse the IPs and report them to their ISP... Probably not.
 
You must log in or register to reply here.
Back
Top