coredump's questions

So, strangest thing happening on Debian PostgreSQL user:

lab3:~# su - postgres
postgres@lab3:~$ plogout
lab3:~# 

And:

lab3:~# su postgres
postgres@lab3:/root$ pexit
lab3:~#

What is happening here? Well, if right after I use su to change to the postgres user, using su - or su, I press p (like I was going to write psql) I get logged out by logout or exit. That doesn't happen if I press enter and then press p on the line below, it only happens if the first thing I press is p. Apparently it happens with any character, but sometimes it fails on e or a.

Are you asking WHAAAAAT? Yeah. Me too. This is happening on all our Debian Lenny machines but not on at least one Squeeze we have.

So, we use Squid 3 here (3.0.STABLE8-3+lenny4), pretty standard configuration (no dansguardian or similar) + NTLM authentication with LDAP background, circa 1000 users on a busy day, and our acls reference some external files (allowed/blocked sites/ip addresses).

On Squid 2.X we used to be capable of reloading it's configuration (to add or sites or addresses to rules, etc) and squid would not stop serving during the reload. Since we changed to 3.0, that seems to be impossible: everytime we use reload (or -k reconfigure) it stop serving requests for as long as 2 minutes, and clients receive a Configured proxy is not accepting connections message.

I checked the documentation and got nothing about it, does anyone else suffer from this problem or is it a isolated case on my setup? Also, if you have Squid 3.0 and doesn't suffer from this problem, how is your squid configured?

So, there're a bunch of questions on SF about the uses and how anycast IPs are cool. My approach is something more practical. What specifically I need to have to use one of those addresses?

• Do I need to be an AS (Autonomous System)?
• If I want to use an Anycast IP on my internal network, is it possible?
• Do I need anything special with a registrar/operator(s) to use it?

Basically, if I want to use an Anycast IP address, what exactly I need, from the equipment to configuration part.

I am searching for good books and articles about TCP/IP, mainly the security aspects of TCP/IP protocols. I have TCP/IP Illustrated and the TCP Guide, but they kinda lack on description of 'classic' attacks and how the internals of protocols relate to those attacks.

PS: Seeing the first real answer made me remember to add that this is strictly for studying purposes, I have no intention of going black hat at this point, I am just preparing for job interviews :)

I will have to deal with some Solaris machines in a couple of months, but I am a born and raised Linux admin (since like, 1997). Even so, Unixes are Unixes and even if they have their differences, many things are easier to grasp.

What I would like are resources and tips from the Server Fault community about the most critical/different points so I can focus on learning those.

I already have: Solaris to Linux Migration (IBM Redbook) and Linux to Solaris Administrators Guide (Sun). Any tips are welcome :)

So, a legacy server of mine was using a PERC (5, if I am not wrong) with Raid 0 and he went down with 2 failed disks. We forced the disks back online but the filesystem is a mess.

Is there any program (like testdisk) that can scan the raid in search of lost data so we can try and get something back? The filesystem is NTFS.

No, no backup for this data.

EDIT: Believe me I agree with every 'raid 0 no backup craziness' comment you all did, but the context is way more complex than that and it was an accepted risk, 1 more week and it would not have happened, but that is the nature of risk analysis, accepted risks and Murphy. We are sending the disks to a data recovery company to see what can be done.