Page 3 of 3

libtermcap and Debian 3.1

Posted: Thu Nov 23, 2006 8:03 pm
by mark
The shared mem shmid will be different every time. They are found by key. Seems like shell environment is somewhat different/isolated from the CGI environment.

What's your login id?
What user id is the CGI running texis as?
What user id owns the license segment?
What are the shared mem and setuid rules for your shared server (ask your web host)?

The key is that texis always run as the same user, whether from shell or CGI.

libtermcap and Debian 3.1

Posted: Thu Nov 23, 2006 8:35 pm
by rjshelq
Something is very odd.... I was going to do another fresh install, but first I killed the monitor and texis processes, then I removed the two memory segments... and then out of foolish curiosity, I clicked on my web browser link for the admin control panel, and it started right up! Then I used my web browser to do searches, and Webinator is running perfectly (at the moment).

As for the ids, when I log in to the shell, my id there is the same as the owner of all the files in my webinator_5 directory, and is the same as the owner of the two memory segments that I deleted... but apparently there are some other memory segments that I cannot see, but which Webinator is happily using.

I don't know how to get the answer to your second question.. how do I find out "What user id is the CGI running texis as?" That may be the key to this oddity.

libtermcap and Debian 3.1

Posted: Thu Nov 23, 2006 10:05 pm
by John
It sounds as if the CGI user can create shared memory segments you can't see, and vice versa, however the system is not letting the id be shared. Is there a license.key with a different owner in the install directory?

You can add a function to the dowalk script to display the user it is running as, e.g.

<A NAME=showuser PUBLIC>
<sysinfo user>
$ret
</A>

and then access it as http://..../dowalk/showuser.html