[geeks] Argh, solaris

[Ryn]

I would also disable the SMC garbage. The SMC framework makes extensive
use of RPC based communication services :( If that doesn't work, enable RPC
and let the bastard program register with it. You can then use rpcinfo to gather
a bit more information. I would also look into lsof once you startup rpcbind.
This
should set you in the right direction.

Ryan

----- Original Message -----
From: "Joshua D Boyd" <jdboyd at cs.millersville.edu>
To: <geeks at sunhelp.org>
Sent: Sunday, April 28, 2002 3:08 AM
Subject: [geeks] Argh, solaris


> I keep getting this error on the console:
> Apr 28 03:02:01 jdb.neurotica.net server[264]: svc_tp_create: Could not
register prog 300598 vers 1 on udp
> Apr 28 03:02:01 jdb.neurotica.net server[264]: svc_tp_create: Could not
register prog 300598 vers 1 on tcp
> Apr 28 03:02:01 jdb.neurotica.net server[264]: svc_tp_create: Could not
register prog 300598 vers 1 on ticlts
> Apr 28 03:02:01 jdb.neurotica.net server[264]: svc_tp_create: Could not
register prog 300598 vers 1 on ticotsord
> Apr 28 03:02:01 jdb.neurotica.net server[264]: svc_tp_create: Could not
register prog 300598 vers 1 on ticots
> Apr 28 03:02:01 jdb.neurotica.net server[264]: unable to create
(DMI2_SERVER, DMI2_SERVER_VERSION) for netpath.
>
> I've disabled every line in /etc/inetd.conf that has rpc in it.
> Before and after the error, my task list is ps -ef:
> bash-2.03# ps -ef
>      UID   PID  PPID  C    STIME TTY      TIME CMD
>     root     0     0  0 02:59:31 ?        0:00 sched
>     root     1     0  0 02:59:34 ?        0:00 /etc/init -
>     root     2     0  0 02:59:34 ?        0:00 pageout
>     root     3     0  0 02:59:34 ?        0:00 fsflush
>     root   207     1  0 03:00:01 ?        0:00 /usr/lib/saf/sac -t 300
>     root   210   207  0 03:00:01 ?        0:00 /usr/lib/saf/ttymon
>     root   175     1  0 02:59:56 ?        0:00 /usr/lib/utmpd
>     root    47     1  0 02:59:44 ?        0:00 /usr/lib/sysevent/syseventd
>     root    49     1  0 02:59:44 ?        0:00 /usr/lib/sysevent/syseventconfd
>     root   126     1  0 02:59:53 ?        0:00 /usr/sbin/inetd -s
>     root   155     1  0 02:59:55 ?        0:00 /usr/lib/lpsched
>     root   138     1  0 02:59:54 ?        0:00 /usr/sbin/cron
>     root   184     1  0 02:59:57 ?        0:02 /usr/sbin/vold
>     root   150     1  0 02:59:54 ?        0:00 /usr/sbin/nscd
>     root   135     1  0 02:59:53 ?        0:00 /usr/sbin/syslogd
>     root   169     1  0 02:59:56 ?        0:00 /usr/lib/power/powerd
>     root   181     1  0 02:59:57 ?        0:00 /usr/sadm/lib/smc/bin/smcboot
>     root   182   181  0 02:59:57 ?        0:00 /usr/sadm/lib/smc/bin/smcboot
>     root   208     1  0 03:00:01 console  0:00 -sh
>     root   220   208  0 03:00:25 console  0:00 bash
>     root   266   220  1 03:03:26 console  0:00 ps -ef
> bash-2.03#
>
> I can't think of anything else to check, nor can I find anything on google,
> other than some pages that say enable rpcbind, which many pages say to disable
> as part of a good security plan.
>
> Further, what script starts lpsched?  This machine has no printer, and will
> never be used to print, so running lpsched is pretty silly.
>
> --
> Joshua D. Boyd
> _______________________________________________
> GEEKS:  http://www.sunhelp.org/mailman/listinfo/geeks