We have decided to go ahead an comment out rpc.ttdbservd and see what
happens....
Thanks for the responses from Toni Harbaugh-Blackford [harbaugh_at_ncifcrf.gov],
Ken S. -- <kschu_at_fnal.gov>,
Charles Hooks [cdhooks_at_astro.psu.edu], and Schrann, Brian
[schrannb_at_uphs.upenn.edu] :
Toni indicated a belief that this will only cause a problem if you are trying to
use ToolTalk across machines, which most people don't. Charles has been
commenting it out and has yet to have a complaint from either the systems or the
user community. Ken reminded us that, after changing inetd.conf and HUP'ing
inetd, to check for any existing service daemons which you still need to kill.
Brian pointed out that it is something quickly turned back on should it's
absence create a problem.
==========================
The original question:
We have been considering commenting out the lines in /etc/inetd.conf which read:
rpc.cmsd/2-4 dgram rpc/udp wait root /usr/dt/bin/rpc.cmsd rpc.cmsd
rpc.ttdbserverd stream rpc/tcp wait root /usr/dt/bin/rpc.ttdbserverd
rpc.ttdbserverd
We are aware that rpc.cmsd is the calendar manager daemon, and not a service we
use.
But we are unsure what will break when we comment out rpc.ttdbservd (ToolTalk
database server). I have commented it out on one of our workstations, which
when rebooted appeared to look the same CDE-wise as before. We thought it might
affect the use of the File Manager window, but I can still open it up and move
around in it. Any ideas/information would be greatly appreciated.
Thanks, Laura Bennett
attached mail follows:
At 01:59 PM 7/14/99 -0400, you wrote:
>We have been considering commenting out the lines in /etc/inetd.conf which
read:
>
>rpc.cmsd/2-4 dgram rpc/udp wait root /usr/dt/bin/rpc.cmsd rpc.cmsd
>rpc.ttdbserverd stream rpc/tcp wait root /usr/dt/bin/rpc.ttdbserverd
>rpc.ttdbserverd
>
>We are aware that rpc.cmsd is the calendar manager daemon, and not a service we
>use.
>But we are unsure what will break when we comment out rpc.ttdbservd (ToolTalk
>database server). I have commented it out on one of our workstations, which
>when rebooted appeared to look the same CDE-wise as before. We thought it
might
>affect the use of the File Manager window, but I can still open it up and move
>around in it. Any ideas/information would be greatly appreciated.
>
We have rpc.ttdbserverd commented out. I think this will only cause a problem
if you are trying to use ToolTalk across machines, which most people don't.
Toni
attached mail follows:
Hi Laura,
I'm sure you are aware that after you comment these service out in the
/etc/inetd.conf file, you need to send a SIGHUP to the inetd process so
that it will re-read the configuration file. What I found is that you
should also look to see if there are any existing service daemons which
you need to kill. I found an rpc.ttdbserverd process running on more than
one of my DEC hosts after I had sent the SIGHUP to the inet daemon.
I'm not sure what software uses the rpc.ttdbservd. It is ToolTalk but
I don't recall what that is. I'm pretty sure that both of these daemons
are for use with SUN products. The 'rpc.cmsd' is the Sun Calendar Manager
Syncronization Daemon, if I remember the acronym right. I took the
approach of "disable them" now and "figure out what to do if someone
complains" later.
More later,
Ken S. -- <kschu_at_fnal.gov>
On Wednesday 14 July 1999 you wrote:
> We have been considering commenting out the lines in /etc/inetd.conf which
> read:
>
> rpc.cmsd/2-4 dgram rpc/udp wait root /usr/dt/bin/rpc.cmsd rpc.cmsd
> rpc.ttdbserverd stream rpc/tcp wait root /usr/dt/bin/rpc.ttdbserverd
> rpc.ttdbserverd
>
> We are aware that rpc.cmsd is the calendar manager daemon, and not a
> service we use. But we are unsure what will break when we comment out
> rpc.ttdbservd (ToolTalk database server). I have commented it out on
> one of our workstations, which when rebooted appeared to look the same
> CDE-wise as before. We thought it might affect the use of the File
> Manager window, but I can still open it up and move around in it.
> Any ideas/information would be greatly appreciated.
--
===============================================================
Ken Schumacher -- Fermilab, Computing Div. / OSS Dept / CSS
kschu_at_fnal.gov MS369 x4579 w:630-840-4579 f:630-840-6345
DEC (Compaq) Liaison -- Liaison Requests: dec-liaison_at_fnal.gov
===============================================================
attached mail follows:
I have been commenting it out of most of our machines due to security reasons.
I have yet to have a complaint from either the systems or the user community.
Charles
> Delivered-To: tru64-unix-managers_at_sws1.ctd.ornl.gov
> Content-return: allowed
> Date: Wed, 14 Jul 1999 13:59:50 -0400
> From: "Bennett, Laura L. \(CIT\)" <lbennett_at_exchange.nih.gov>
> Subject: Can we comment out rpc.ttdbservd?
> To: "'tru64-unix-managers_at_ornl.gov'" <tru64-unix-managers_at_ornl.gov>
> MIME-version: 1.0
>
> We have been considering commenting out the lines in /etc/inetd.conf which
read:
>
> rpc.cmsd/2-4 dgram rpc/udp wait root /usr/dt/bin/rpc.cmsd rpc.cmsd
> rpc.ttdbserverd stream rpc/tcp wait root /usr/dt/bin/rpc.ttdbserverd
> rpc.ttdbserverd
>
> We are aware that rpc.cmsd is the calendar manager daemon, and not a service
we
> use.
> But we are unsure what will break when we comment out rpc.ttdbservd (ToolTalk
> database server). I have commented it out on one of our workstations, which
> when rebooted appeared to look the same CDE-wise as before. We thought it
might
> affect the use of the File Manager window, but I can still open it up and move
> around in it. Any ideas/information would be greatly appreciated.
>
> Will summarize.....
> Thanks, Laura Bennett
>
> -------------------------------------------------------
> Laura Bennett
> lbennett_at_exchange.nih.gov
> National Institutes of Health
> CIT/DCSS/ESSS
>
------------------------------------------------------------------
Charles Hooks Manager, Network and Information Systems
Penn State University Dept. of Astronomy and Astrophysics
525 Davey Lab 814-863-7111
cdhooks_at_astro.psu.edu www.astro.psu.edu
------------------------------------------------------------------
attached mail follows:
Laura,
My $0.02... for what it's worth... One of the first things you are
instructed to do, when hardening a server for firewall use, is to comment
out the services in /etc/inetd.conf (at least where Solaris and FireWall-1
are concerned). The server still functioned... but potential security holes
where shut down. Your server will still function, but that service will be
unavailable. You can always go ahead and disable the service and if you
notice any quirky behavior, reenable the individual services that you
commented out.
> -----Original Message-----
> From: Bennett, Laura L. (CIT) [SMTP:lbennett_at_exchange.nih.gov]
> Sent: Wednesday, July 14, 1999 2:00 PM
> To: 'tru64-unix-managers_at_ornl.gov'
> Subject: Can we comment out rpc.ttdbservd?
>
> We have been considering commenting out the lines in /etc/inetd.conf which
> read:
>
> rpc.cmsd/2-4 dgram rpc/udp wait root /usr/dt/bin/rpc.cmsd rpc.cmsd
> rpc.ttdbserverd stream rpc/tcp wait root /usr/dt/bin/rpc.ttdbserverd
> rpc.ttdbserverd
>
> We are aware that rpc.cmsd is the calendar manager daemon, and not a
> service we
> use.
> But we are unsure what will break when we comment out rpc.ttdbservd
> (ToolTalk
> database server). I have commented it out on one of our workstations,
> which
> when rebooted appeared to look the same CDE-wise as before. We thought it
> might
> affect the use of the File Manager window, but I can still open it up and
> move
> around in it. Any ideas/information would be greatly appreciated.
>
> Will summarize.....
> Thanks, Laura Bennett
>
> -------------------------------------------------------
> Laura Bennett
> lbennett_at_exchange.nih.gov
> National Institutes of Health
> CIT/DCSS/ESSS
Received on Thu Jul 22 1999 - 17:40:32 NZST