Re: ioo / vmo

• Previous message: Ferenc Gyurcsan: "Re: ioo / vmo"
• Maybe in reply to: Mike Tibor: "ioo / vmo"
• Next in thread: Mike Tibor: "Re: ioo / vmo"
• Reply: Mike Tibor: "Re: ioo / vmo"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Date:         Mon, 31 Jan 2005 14:58:10 -0600
To: aix-l@Princeton.EDU

There are files in /etc/tunables that need to have the correct
permissions also. This will determine what happens on your next reboot.
Here's what I have in that directory.

-rw-r--r-- 1 root system 65 Dec 13 09:11 lastboot.log
-rw-r--r-- 1 root system 10964 Dec 13 09:11 lastboot
-rw-r--r-- 1 root system 2082 Dec 13 10:24 nextboot

Sounds like someone may have gotten a little crazy with wildcarded
permissions of 0000. I'd go through your other directories and see if
anything else was affected. /etc and /usr are fairly important.

Regards,
Darryl

-----Original Message-----
From: IBM AIX Discussion List [mailto:aix-l@Princeton.EDU] On Behalf Of
Mike Tibor
Sent: Monday, January 31, 2005 2:34 PM
To: aix-l@Princeton.EDU
Subject: ioo / vmo

I'm trying to get/set some parameters using ioo and vmo on my p570
running 5.3, and I'm running into some goofy file permissions problems.
By default, it appears that a large number of files in /usr/bin and
/usr/sbin have 0000 permissions. This includes ioo* and vmo*. I set
ioo, ioo64, vmo and vmo64 to 0550, but now I'm getting the following:

   root@aixdb2-1:/usr/sbin# ioo -a
   ioo: 1485-121 Error reading tunables from nextboot file

Are there other files ioo may be trying to call which are mode 0000?
I've already found and chmod'd /usr/sbin/tun*, but that didn't help.

Anybody know why these files are mode 0000 by default?

Thanks,
Mike

• Previous message: Ferenc Gyurcsan: "Re: ioo / vmo"
• Maybe in reply to: Mike Tibor: "ioo / vmo"
• Next in thread: Mike Tibor: "Re: ioo / vmo"
• Reply: Mike Tibor: "Re: ioo / vmo"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]