Paul, Thanks for the information. What would be the great frustration, to me & I'm not currently using 10G, is that Oracle has these "root" daemons that they spawn in this way. If it's an Oracle needed process it should be controlled from the dbstart script, not an inittab entry. Dick Goulet Senior Oracle DBA Oracle Certified 8i DBA -----Original Message----- From: Paul Drake [mailto:bdbafh@xxxxxxxxx]=20 Sent: Wednesday, January 26, 2005 7:17 PM To: oracle-l Subject: dba job security - even better if you're also the sysadmin 10g - you won't need a dba http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_d atabase_id=3DFOR&p_id=3D611535.995 if O'Reilly ever puts out an "Oracle Annoyances" book, having ocssd running for non-ASM, non-clustered installations in a respawn mode without supplying the wooden stake to kill the unholy beast - well, it gets my vote. Yes, I commented out the line in the file /etc/inittab, but I do not care to reboot this server on which I barely have a decent connection thru vnc with no sysadmin at that site for another week. a reboot could mean an unscheduled trip to Minnesota, which might even be more inhospitable than Pittsburgh was last Sunday. Yes, someone was nice enough to post the following on the thread listed above: [root@mybox root]# /etc/init.d/init.cssd stop Shutting down CRS daemon. Shutting down EVM daemon. Shutting down CSS daemon. Shutdown request successfully issued. Is that too difficult to include in a note, or even in the 10.1.0.3 patchset? btw - Oracle has re-released the 10g R1 for lin32 as 10.1.0.3, just like they did for the 9i R2 as 9.2.0.4. grumble. Paul - back to bdbafh mode. -- //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l