The problem does not go away when all users are disconnected. The problem
also doesn't go away when everybody logs off the Novell server. The problem
(the ghost users and locks) only goes away when we reboot the server. If
Novell is hanging onto the ghost users and locks I think we should be able
to see them with Monitor which we cannot.
_______________________________________
At 07:25 PM 4/26/2001 -0400, you wrote:
>Question......what makes you think that it is Novell that is hanging on
>to the ghost users, rather than Rbase locking the tables as if the User
>were still connected? Does the problem go away if you disconnect all
>users by "brute force" (booting all stations, but leaving the Server
>alone)?
>
>Mike Sinclair
>
>
>Bernie Corrigan wrote:
>>
>> 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?
>
>
