4mula1;262171 Wrote:
Since dtrace shows that the process that calls for /etc/protocols is
slimserver.pl and not perl I hadn't considered all of the perl modules
at play being responsible. I've never run across /etc/protocols before
and was a little curious.
There's some more information
I started an rsync job last night on my Solaris box and it was still
running this morning (and still running now!) so I wanted to see if I
could figure out how much it had done. It was scheduled via cron so I
have no output on it. I had the idea to use Dtrace to show what files
were being opened
Just guessing, but usage of perl's IO::Socket module may trigger reading
this file.
--
jth
jth's Profile: http://forums.slimdevices.com/member.php?userid=48
View this thread:
That may very well be. Since dtrace shows that the process that calls
for /etc/protocols is slimserver.pl and not perl I hadn't considered
all of the perl modules at play being responsible. I've never run
across /etc/protocols before and was a little curious.
It's really amazing how many files
4mula1;262171 Wrote:
It's really amazing how many files get opened every time I log in via
ssh...
Which is why Unix boxes use all unallocated memory for buffers/cache.
Some files are accessed a zillion times... and why nscd rocks so much
on servers with a ton of users... getpwent() and
I've noticed that nscd, utmpd, init, and automountd are all busy little
beavers. SlimServer is a lot busier than I thought but I do use the
SuperDateTime plugin (for weather) and the RSS screensaver. I have a
feeling those are the reasons that the SlimServer filecache is hit as
often as it is.
