I am not sure I understand how you are starting MQ. Init does not go through login, so init will not get the other groups for root.
I think that login sets the groups for root on our SuSE 10 system, but I can't check right now. -----Original Message----- From: Linux on 390 Port on behalf of Arty Ecock Sent: Tue 3/20/2007 4:24 AM To: [email protected] Subject: getgroups for root Hi, I'm running into a strange problem with SLES9. We are doing a TIM/TAM rollout and a software component (MQ) is complaining during startup. It seems that the user that runs the start script (root, during boot in our case) does not appear to be in the mqm group. An "id" command issued from the 3215 console confirms. A "cat /etc/groups" contradicts, as does a "sudo id". If we run the start script from an ssh session, it works (as does the "id" command). It turns out that "login" might be the culprit, as it only sets the primary group if the uid is 0. I tried removing minigetty from /etc/inittab, and tried "sulogin", Rick's suloginv script, and /bin/sh all to no avail. I really don't mind login's behaviour, but the rc scripts run before login, so shouldn't root's list of auxiliary groups be set by getgroups properly during boot? Cheers, Arty ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
