I don't think sweeping will stop users logging in. A more likely
reason is...
Users are logged in to the server on TCP/IP. (SERVER:C:\dATA ETC)
Someone then logs in, using the server as a client, as a Local
Server, not using TCP/IP.(c:\DATA ETC).
The server then starts screwing up the database because it is
treating the same file as two separate databases. This often
prevents further logins. If you are very lucky, the lock-outs happen
before any significant data or metadata updates are made, or you kill
the server before any significant transactions get committed, and you
don't corrupt the entire database.

So ensure that all log-ins are using the same protocol, and precisely
the same path to the database file.

--- In ib-support@y..., "Richard Pendered" <rpendered@t...> wrote:


> not wierd behavour, it is doing a garbage sweep. set the sweep
interval to 0
> and run sweep once a day/week with cron.....
>
> -----Original Message-----
> From: proguy_dk [mailto:firebird@p...]
> Sent: 23 January 2002 15:35
> To: ib-support@y...
> Subject: [ib-support] Firebird 1.0 goes boom
>
>
> Hi there,
>
> We have an Firebird 1.0 Server running on our Linux server,
> which mostly works fine. But once in a while it suddenly goes boom,
> takes all available processing power, and locks-up - no connections
> are possible to the server anymore.
>
> Any suggestions to what could be causing this weird behavour?
>
> // Paul Fleischer
>
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@e...
>
>
>
> Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/