Disabling PVSW.LOG file under Btrieve 7.01 Workstation Engine 
Author Message
 Disabling PVSW.LOG file under Btrieve 7.01 Workstation Engine
As a user of Btrieve 7.0 Workstation engine, I'd like to
disable the creation and the updating of the PVSW.LOG file.
Whereas I desactived any log from the registry, (Logging
entry from Pervasive Software\Microkernel Workstation
Engine\Version 7.01\Settings is set to NO as Trace entry...)
Is there a way to Disable definitively PVSW.LOG file ?

Thanks in advance.
Chris.



Tue, 01 Jun 2004 23:22:34 GMT
 Disabling PVSW.LOG file under Btrieve 7.01 Workstation Engine

This log provides diagnostic information in case problems appear.  Why
would you want to disable it?  If the log is growing very rapidly, then
there is a problem being reported in there which should be fixed.

Since the log is not held open, you can always delete the file at
startup -- via AUTOEXEC.BAT, for example -- but I would recommend
leaving it alone.
 Goldstar Software Inc.
 Building on Btrieve(R) for the Future(SM)
 Bill Bach

 http://www.goldstarsoftware.com
 *** Pervasive.SQL Service & Support Courses ***
 Chicago: February 5-8, 2001 - See our web site for details!

Quote:

> As a user of Btrieve 7.0 Workstation engine, I'd like to
> disable the creation and the updating of the PVSW.LOG file.
> Whereas I desactived any log from the registry, (Logging
> entry from Pervasive Software\Microkernel Workstation
> Engine\Version 7.01\Settings is set to NO as Trace entry...)
> Is there a way to Disable definitively PVSW.LOG file ?

> Thanks in advance.
> Chris.



Wed, 02 Jun 2004 01:54:14 GMT
 Disabling PVSW.LOG file under Btrieve 7.01 Workstation Engine
I concur.

If you really don't want to be bothered with what might be important
messages, you could always flush (delete) the log file at reboot. If
something goes seriously wrong though, you'll never know what hit you
(you may interpret this line any way you like). Just leave it...


Quote:
>This log provides diagnostic information in case problems appear.  Why
>would you want to disable it?  If the log is growing very rapidly, then
>there is a problem being reported in there which should be fixed.

>Since the log is not held open, you can always delete the file at
>startup -- via AUTOEXEC.BAT, for example -- but I would recommend
>leaving it alone.
> Goldstar Software Inc.
> Building on Btrieve(R) for the Future(SM)
> Bill Bach

> http://www.goldstarsoftware.com
> *** Pervasive.SQL Service & Support Courses ***
> Chicago: February 5-8, 2001 - See our web site for details!


>> As a user of Btrieve 7.0 Workstation engine, I'd like to
>> disable the creation and the updating of the PVSW.LOG file.
>> Whereas I desactived any log from the registry, (Logging
>> entry from Pervasive Software\Microkernel Workstation
>> Engine\Version 7.01\Settings is set to NO as Trace entry...)
>> Is there a way to Disable definitively PVSW.LOG file ?

>> Thanks in advance.
>> Chris.

 Gordon Bos
 Q-RY Solutions
 +31-(0)15-2564035

 http://www.q-ry.nl/



Wed, 02 Jun 2004 02:57:52 GMT
 Disabling PVSW.LOG file under Btrieve 7.01 Workstation Engine
This log should not grow at much  if the system, network and
application are healthy.

There are two other logging settings.
One for individual file logging... adds the capability to rollforward
from last snapshot with log rotation (manual process) to the last
logged entry.  By default this one is off, and even turning it on does
not actually start the logging until the files are added to the
configuration list.
The other has to do with logging transactions.  "Transaction
Durability" logging.  By default this one is now on.  The transaction
durability logs are not human readable and are used to roll forward
completed application transactions that have not completed their
system transaction from the cache to the data file.  By default this
window is set to 10 seconds so is small.

Leonard

On Fri, 14 Dec 2001 19:57:52 +0100, Gordon

Quote:

>I concur.

>If you really don't want to be bothered with what might be important
>messages, you could always flush (delete) the log file at reboot. If
>something goes seriously wrong though, you'll never know what hit you
>(you may interpret this line any way you like). Just leave it...


>>This log provides diagnostic information in case problems appear.  Why
>>would you want to disable it?  If the log is growing very rapidly, then
>>there is a problem being reported in there which should be fixed.

>>Since the log is not held open, you can always delete the file at
>>startup -- via AUTOEXEC.BAT, for example -- but I would recommend
>>leaving it alone.
>> Goldstar Software Inc.
>> Building on Btrieve(R) for the Future(SM)
>> Bill Bach

>> http://www.goldstarsoftware.com
>> *** Pervasive.SQL Service & Support Courses ***
>> Chicago: February 5-8, 2001 - See our web site for details!


>>> As a user of Btrieve 7.0 Workstation engine, I'd like to
>>> disable the creation and the updating of the PVSW.LOG file.
>>> Whereas I desactived any log from the registry, (Logging
>>> entry from Pervasive Software\Microkernel Workstation
>>> Engine\Version 7.01\Settings is set to NO as Trace entry...)
>>> Is there a way to Disable definitively PVSW.LOG file ?

>>> Thanks in advance.
>>> Chris.

> Gordon Bos
> Q-RY Solutions
> +31-(0)15-2564035

> http://www.q-ry.nl/



Wed, 02 Jun 2004 15:01:16 GMT
 
 [ 4 post ] 

 Relevant Pages 

1. Workstation engine access to a Btrieve file on a Netware Server freeses programm or computer

2. Btrieve 7 Server and Btrieve 6.15 Workstation Engine

3. Btrieve 7.01 and Magic 7.11a

4. BUTIL -RECOVER under Btrieve 7.01 ?

5. BTrieve workstation engine

6. Btrieve 6.15 for Windows Workstation Engine and Windows 2000

7. LOAD BTRIEVE v6.15 WORKSTATION ENGINE

8. Btrieve 6.15 Workstation Engine and Citrix

9. Status 81 in Btrieve 6.15 Workstation Engine

10. status 101 / workstation engine and workstation application running on WinNT server

11. Status 2 with workstation engine accessing files on Netware 3.12

12. SWsoft OLEDB vs PVSW OLEDB/ PVSW problems


 
Powered by phpBB® Forum Software