Troy -
According to the system manager, an NT type: When she examined
file/lock activity on all the rb? files there wasn't any. The place is so
chaotic we don't know what service pack is installed. Our current guess is
none or 2 based on disks we have found. I will suggest the upgrade to
Novell 5. How does one tell which service pack has been applied?
Bernie
_______________________________________
At 08:05 AM 4/27/2001 -0600, you wrote:
>You need to go into file/lock activity and select the #1 file. This will
>show you all of the conncetions that have the file open. Next you go find
>the offending connection on the connections screen and press delete. If
>you don't find on the #1 file, check #2,#3, and #4. If the you can't see
>the connection from the console, but the files are still locked, make sure
>you have the latest Netware 4 service pack installed.
>
>Upgrade to Netware 5. I never have this problem.
>
>Troy Sosamon
>Denver, Co.
>
>===== Original Message from [EMAIL PROTECTED] at 4/26/01 5:36 pm
>>This is a replay of a message I posted in December of 2000. The ghost user
>>problem with RBase for Windows 6.5+ has has continued. Whenever a user
>>crashes or exits improperly, say by turning off a machine accidentally, that
>>user remains connected to the database until the server is rebooted. This
>>is on Novell 4.11. We wind up with a gradually increasing number of
>>connected users and locked tables as this process continues through time.
>>Is there any way to disconnect the users.
>>
>>Novell Monitor does not show the connections. According to Monitor no one
>>is using the R:Base files who is not currently really connected so Monitor
>>can't be used to get rid of them. It was my understanding that Novell is
>>supposed to get rid of such connections/locks after about 10 minutes if the
>>user has gone away. Is there some setting I should be looking at that would
>>cause Novell not to do this?
>
>
>
