Comments on: udev for Security Conscious RAC Sysadmins http://www.ardentperf.com/2007/02/26/udev-for-security-conscious-rac-sysadmins/ Jeremy Schneider Wed, 30 Nov 2011 21:26:13 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Oracle Clusterware on RHEL5/OEL5 with udev and multipath : Ardent Performance Computing http://www.ardentperf.com/2007/02/26/udev-for-security-conscious-rac-sysadmins/#comment-826 Oracle Clusterware on RHEL5/OEL5 with udev and multipath : Ardent Performance Computing Thu, 14 Feb 2008 05:38:47 +0000 http://www.ardentperf.com/2007/02/26/udev-for-security-conscious-rac-sysadmins/#comment-826 [...] exactly one year ago I wrote about using udev on 2.6 kernels to set the proper permissions for Oracle RAC. Two weeks after that post (March 14) Red Hat [...] [...] exactly one year ago I wrote about using udev on 2.6 kernels to set the proper permissions for Oracle RAC. Two weeks after that post (March 14) Red Hat [...]

]]> By: Walid Shaari http://www.ardentperf.com/2007/02/26/udev-for-security-conscious-rac-sysadmins/#comment-778 Walid Shaari Sat, 29 Sep 2007 09:52:39 +0000 http://www.ardentperf.com/2007/02/26/udev-for-security-conscious-rac-sysadmins/#comment-778 I had problems with rules in RHEL4U4 and it does not seem to work as documented for IBM storage DS4800 using the mpp driver, but if i reboot i can see the raw devices created, but if i try udevtest it does not seem to work I had problems with rules in RHEL4U4 and it does not seem to work as documented for IBM storage DS4800 using the mpp driver, but if i reboot i can see the raw devices created, but if i try udevtest it does not seem to work

]]> By: David Perez http://www.ardentperf.com/2007/02/26/udev-for-security-conscious-rac-sysadmins/#comment-680 David Perez Sat, 14 Jul 2007 18:06:11 +0000 http://www.ardentperf.com/2007/02/26/udev-for-security-conscious-rac-sysadmins/#comment-680 Yea I got it to work, after several reboot it suddently started to work... Yea I got it to work, after several reboot it suddently started to work…

]]> By: Jeremy http://www.ardentperf.com/2007/02/26/udev-for-security-conscious-rac-sysadmins/#comment-675 Jeremy Thu, 12 Jul 2007 15:00:29 +0000 http://www.ardentperf.com/2007/02/26/udev-for-security-conscious-rac-sysadmins/#comment-675 Hey sorry for the slow response - I was on vacation much of last week. :) Anyway, I don't have anything earth-shattering to add... I didn't mess around with the RULES much, just the PERMISSIONS. I've always left the default names for raw devices. Have you gotten this to work since you posted the comment last week? Hey sorry for the slow response – I was on vacation much of last week. :)

Anyway, I don’t have anything earth-shattering to add… I didn’t mess around with the RULES much, just the PERMISSIONS. I’ve always left the default names for raw devices. Have you gotten this to work since you posted the comment last week?

]]> By: David Perez http://www.ardentperf.com/2007/02/26/udev-for-security-conscious-rac-sysadmins/#comment-570 David Perez Wed, 04 Jul 2007 05:04:41 +0000 http://www.ardentperf.com/2007/02/26/udev-for-security-conscious-rac-sysadmins/#comment-570 Hi Have you tried create devices under /dev using this rule? KERNEL="sd?1", BUS="scsi", PROGRAM="/sbin/scsi_id", RESULT="3600143800005eda0b43b826e900e000f", NAME="ocr" In RHEL 4 U5 does not seem to work, permissions neither Hi

Have you tried create devices under /dev using this rule?

KERNEL=”sd?1″, BUS=”scsi”, PROGRAM=”/sbin/scsi_id”, RESULT=”3600143800005eda0b43b826e900e000f”, NAME=”ocr”

In RHEL 4 U5 does not seem to work, permissions neither

]]> By: Single Oracle Password File on Raw with RAC : Ardent Performance Computing http://www.ardentperf.com/2007/02/26/udev-for-security-conscious-rac-sysadmins/#comment-37 Single Oracle Password File on Raw with RAC : Ardent Performance Computing Thu, 22 Mar 2007 00:06:41 +0000 http://www.ardentperf.com/2007/02/26/udev-for-security-conscious-rac-sysadmins/#comment-37 [...] Make sure the raw device has the proper permissions. At a minimum these should match the permissions assigned by the orapwd utility: 640, owned by the oracle user and the oinstall group. For details about how to set this up see my previous post about udev. [...] [...] Make sure the raw device has the proper permissions. At a minimum these should match the permissions assigned by the orapwd utility: 640, owned by the oracle user and the oinstall group. For details about how to set this up see my previous post about udev. [...]

]]>