There are reasons you should not delete the entire {STAF/DataDir}
directory as then you are deleting all data (including data that is
supposed to be "persistent" -- retained whenever STAFProc is restarted)
that is stored by STAF and its services, not just log files. If you
really wanted to get rid of all STAF logs (any STAF log file created by
any STAF service, testcase, etc), you could get rid of the
{STAF/DataDir}/service/log directory. If you just want to get rid of the
STAX logs, you could delete the files in the
{STAF/DataDir}/service/log/MACHINE/{STAF/Config/MachineNickname}/GLOBAL
directory that begin with "STAX_". Or, note that STAX provides a
CLEARLOGS option that you can enable when configuring the STAX service so
that STAX Job and Job User logs are deleted before a job is executed.
If you use the ResPool service, you'll be deleting any resource pools
created by the ResPool service as they are stored in
{STAF/DataDir/service/respool (and these resource pools are supposed to be
persistent) so that isn't good. The same is true for other services that
store persistent data (e.g. LifeCycle, Event, EventManager, Cron,
Namespace, plus many more services so deleting the entire {STAF/DataDir}
directory can cause them not to work as expected.
Also, note that STAX stored the Jython version it requires the first time
the STAX service is registered within the
{STAF/DataDir}/lang/java/shared_jython directory, including a flag that
indicates whether it doesn't need to be reloaded so if you delete the
{STAF/DataDir} directory, it will be reloading Jython each time STAFProc
is restarted (which means the STAFProc startup time will be a little
longer).
STAX also stores the last result from each job ID run in
{STAF/DataDir}/service/stax/job directory. So, if you delete this
directory and restart STAFProc, a STAX GET RESULT JOB <JobID> can only to
used to access the result of STAX jobs run since STAFProc was restarted
(which may or may not be what you wanted).
Note that each time STAFProc is started, it automatically deletes any data
in the {STAF/DataDir}/tmp directory as this is where truly temporary data
is stored.
--------------------------------------------------------------
Sharon Lucas
IBM Austin, luc...@us.ibm.com
(512) 286-7313 or Tieline 363-7313
From: Tennis Smith <tennis_sm...@yahoo.com>
To: staf-users@lists.sourceforge.net,
Date: 06/22/2012 01:12 PM
Subject: [staf-users] Staf/data directory
Hi,
I delete the c:\staf\data directory at system boot time _before_ staf/stax
is started. Staf and stax both seem to start ok afterwards.
Is there any reason why this is a bad idea? It certainly makes clearing
old logs easier.
--
Tks,
-Tennis
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
staf-users mailing list
staf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/staf-users
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
staf-users mailing list
staf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/staf-users
