On Thu, 30 Nov 2006, in the Usenet newsgroup alt.os.linux.ubuntu, in article
Post by BaronPost by Moe TrinAnd the reason you are running portmapper is?
Good question ! I didn't know I was !
"ps sfux" "nobody 2531 vzs=1556, tty=420, stat=S, 19:00 /sbin/portmap
But I do now !
There are several culprits - but it's likely started out of the boot
scripts. It _may_ be being used by sgi-fam which was used by KDE.
This is one reason when trying a new distribution - whether a new
distributor, or just an upgrade, we always spend a lot of time poking
at it - seeing exactly what it's doing. One part of that is a quick
look at the netstat output to see if there are any surprises. I'm getting
less involved in it, but our procedure was that five or six of us would
go into the lab with a new CD set, and play around with it on test boxes
for as long as it takes (average about a week) to come up with some
agreement of what the new release standard is going to look like - what
gets installed, what not. Once we get to that stage, we install it onto
a number of additional test systems that mirror our main servers, and
normal workstation configurations. We then run that for an eight week
backup cycle, to see if anything scary happens. If all is well, a crew
comes in over a weekend, and upgrades all systems. Monday morning might
be a little exciting, but I only remember having to roll back an upgrade
once, and that was only the print servers. I should also mention that
sometimes, the agreement was a resounding "we ain't goin' to install
this pig anywhere!". Red Hat 7.0 was one of those, but there were others.
Post by BaronPost by Moe TrinPost by BaronFind was shown in top.
'ps afux' and see what started 'find'. This wouldn't be the
nightly cron job that updates the 'locate' data base would it? My
systems run 24/7, so that runs via vixie-cron around 4 AM.
Nothing listed for "find"
It wouldn't be. Depending on the distribution, the job may be called
'updatedb' or similar. It's normally run at oh-dark-thirty when few
users are expected, because it's a real resource hog. Systems not
running 24/7 may be running anacron or fcron, and these run the
job some amount of time after power-on. You'll see posts to newsgroups
of people wondering what the heck is going on with all the disk
activity and slow keyboard response. If they're smart, they may do a
'ps -aux' or 'top' and see that "nobody" is running "find" and is
sucking CPU cycles like it's going out of style. They then wonder if
they've been r00ted or something.
Post by BaronPost by Moe TrinProblem is the drives tend to be old and small. I think the largest
drive I have is 7 Gigs, and most of them are smaller than 4 Gigs.
Most of my SCSI stuff is 4 or 9 Gb
How about some Seagate ST11200Ns (1050 Meg) ;-) I think I've got
six of them, as well as a few ST12400Ns (2100 Meg).
Post by BaronWell the new drive came this morning! 36Gb 10K Maxtor. I will try and
get it installed this weekend.
We don't see that many Maxtors, but we tend to avoid the 10K drives as
they seem to run hotter than the 5400 or 7200 RPM drives. As it gets
hot here in the summer (+40C is late Spring or early Fall - it can get
to +50C), our buildings - even the server rooms - are usually at 25 to
30C. That doesn't leave all that much margin for running a hot disk
drive, never mind a bunch of them.
Post by BaronI was going to put swap on "sdc1" along with Kubunto and let SuSE share
it.
Depends on how much RAM you have - we try to avoid hitting swap for
more than low priority stuff. None the less, having a common swap is
definitely correct.
Post by BaronPut "Home" on "sdb1" and "Root, boot et al on the new "sda1" That
will give me 36Gb sda, 9Gb sdb and 4Gb sdc.
Minor item - make sure all the systems are using the same file system
type for home. When Red Hat introduced ext3 in 7.2, I had an interesting
meltdown because I was sharing /home with a Debian install that was still
on ext2. Others may want to use a Reiser File System in place of ext3
which isn't compatible.
Post by BaronThe other 4Gb sdd as scratch.
Interesting name for /tmp/ and/or /var/tmp ;-)
Old guy