/INFORMIXTMP

Hi, I just found a strange behaviour of my IDS 7.30UC9-1 on a Sun Ultra 60 using Solaris 2.6. I installed the IDS, configured a basic onconfig file and run oninit -i. The root dataspace was created and I could start the server with onmode. There was *no* message of any trouble in the logfile. When I used onspaces to create a new chunk I got a message that shared memory was not configured properly. I vaguely remembered of a similar problem and found, that no /INFORMIXTMP had been created. I decided to create this, set group and owner to informix and chmod'ed 660. onspaces showed the same problem. Then I chmod'ed a+rwx to /INFORMIXTMP and from there on onspaces worked fine. Is this a known bug? Should informix create the /INFORMIXTMP on its own and what attributes are to set for this directory? TIA Axel

Axel Sander wrote: > > Hi, > > I just found a strange behaviour of my IDS 7.30UC9-1 on a Sun Ultra 60 > using Solaris 2.6. > > I installed the IDS, configured a basic onconfig file and run oninit -i. > The root dataspace was created and I could start the server with onmode. > There was *no* message of any trouble in the logfile. > When I used onspaces to create a new chunk I got a message that shared > memory was not configured properly. > I vaguely remembered of a similar problem and found, that no /INFORMIXTMP > had been created. I decided to create this, set group and owner to informix > and chmod'ed 660. onspaces showed the same problem. Then I chmod'ed a+rwx > to /INFORMIXTMP and from there on onspaces worked fine. > > Is this a known bug? Should informix create the /INFORMIXTMP on its own and > what attributes are to set for this directory? The /INFORMIXTMP directory should be owned by root, group informix, with permissions 775. Since the root directory is normally not writable by anyone but root so you may have to start the engine as root the first time so make sure the directory is created at init time. Otherwise you can, as you have, create it by hand. Art S. Kagel

On Thu, 02 Dec 1999 14:48:52 -0500, "Art S. Kagel" <kagel@bloomberg.net> wrote: >The /INFORMIXTMP directory should be owned by root, group informix, with >permissions 775. THX for this information. >Since the root directory is normally not writable by >anyone but root so you may have to start the engine as root the first time >so make sure the directory is created at init time. Is this 'first start' mentioned in the installation manual or the 'Administrator's guide' ? I can only remember, that either 'root' or 'informix' can start the engine, so I always (2 times ;-) started as 'informix' and always ran into this trouble. Thanks, Art. Axel

Axel Sander wrote: > On Thu, 02 Dec 1999 14:48:52 -0500, "Art S. Kagel" <kagel@bloomberg.net> > wrote: > > >The /INFORMIXTMP directory should be owned by root, group informix, with > >permissions 775. > THX for this information. > > >Since the root directory is normally not writable by > >anyone but root so you may have to start the engine as root the first time > >so make sure the directory is created at init time. > Is this 'first start' mentioned in the installation manual or the > 'Administrator's guide' ? I can only remember, that either 'root' or > 'informix' can start the engine, so I always (2 times ;-) started as > 'informix' and always ran into this trouble. > > Thanks, Art. > > Axel Hi, I think it should not make much difference who starts the engine first as the owner of "oninit" should be root and sticky bit set. Right? (I did not test it). Regards -- Helmut Leininger Bull AG / Vienna Open Systems Support Email: h.leininger@bull.at helmut.leininger@bull.net This opinion is mine and not necessarily that of my employer. No guarantees whatsoever.