On Jul 15, 11:37, Nash Kristine L. wrote: > Subject: Locking problem > ... If I am logged in as ingres, I can create databases. When I am logged > in as a regular user I can't create any. The regular user has all privileges > except super-user. > > E_DU3190_BAD_LKINIT > Couldn't initialize the locking system for this process. > Please insure that the process is properly installed and that > you have sufficient privilege and system resources to invoke it. > #1 make sure createdb is set-user-id to user ingres: -rws--x--x 1 ingres staff 1667580 Jan 30 1995 createdb #2 make sure you aren't trying to run createdb over ingres-net, you have to run it on the machine where the dbms server is running. (i think you get a different message for that, though. my money is on #1.) -- Karl Schendel Phone: (412) 963-8844 Telesis Computer Corp Fax: (412) 963-1373 wiz@telesis.com From: sweeney@ingres.co.uk (Tony Sweeney) Subject: Re: Locking problem Date: 16 Jul 1996 19:01:56 +0100 In articlewrites: :Hi everyone. : :Can anyone help me? : :I have just installed an additional Ingres License (ver. 6-4/3, Dec :Ultrix 4.2a). :If I am logged in as ingres, I can create databases. When I am logged :in as a :regular user I can't create any. The regular user has all privileges :except :super-user. : :I get the following error: : :E_DU3190_BAD_LKINIT :Couldn't initialize the locking system for this process. :Please insure that the process is properly installed and that :you have sufficient privilege and system resources to invoke it. : :Has anyone ever gotten this error? How did you fix it? You will see this error if createdb does not have the setuid bit set. Createdb needs to attach to the locking and logging shared memory segments owned by ingres in a running installation, and needs its effective userid to be ingres in order to do this. Here is what the permissions should look like on Solaris 2.5: sweeney@troll% ls -l `which createdb` -rws--x--x 1 ingres source 1151600 May 11 15:39 /ingres63p/install/64/05/ingres/bin/createdb sweeney@troll% Ultrix may need the read bit set for group and/or other depending on how you are set up. Also, some unixes handle setuid differently if the real or target user has a uid < 100, so you're probably best off ensuring that both ingres and all ingres users have uids > 100. : :Thanks for your time! Kristine. : Hope this helps. Tony.
© William Yuan 2000
Email William