nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

src.xxxx logs

Using OpenDeploy 5.5.1 sp2, we have implemented filelist deployments using the -inst flag. Average number of deployments per hour is 200 and we deploy to two servers. This causes a great many log files to be generated since there are 3 created with each deployment. Is there a way to disable the creation of these log files?

Thanks,
Gwen

Find more posts tagged with

Comments

Change the logfile location to /dev/null, though someone once
noted that /dev/null was filling up. Smiley Wink

The logfiles are your means of debugging something should a deployment fail. It would be better to set up a process to remove all src.* logfiles that are N days old than to not generate them or to try to generate them in /dev/null (if that even works, haven't tried)

--fish
(Interwoven Senior Technical Consultant)

Thank you for the input. We have already implemented a removal script, but I was hopeful that there would be a way to turn it off.

Thanks,
Gwen

Nope - no way to turn it off that I'm aware of - and I think doing so would actually impose a significant change to the product (i.e. not a trivial patch) which ultimately would make it significantly more difficult to debug problems found in the field ....

--fish
(Interwoven Senior Technical Consultant)

In an ideal situation.... we would be able to queue more than one job and logging would be to only three src.xxxx files... If that were the case, the log files would be more useful. From my standpoint that needs to be where programming changes would be beneficial, increasing number of deployments which can be queued.

Gwen

It's risky to remove log files that haven't been rolled over, since they may still be in use. Consider setting a low rollover threshold value for the log files, and then delete or archive ones that have been rolled over.

Another thing to consider... if you can do differential deployments instead of file list, then the current simple queuing mechanism may work out since the most recently submitted job is pended, which should pick up all changes that occurred since the last job that ran.

Todd Scallan
Group Product Manager
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com

Log files being removed are at least 15 minutes old. Since only 2 files are included per deployment, only takes a second or two and the log files are never written to again. 15 minute delay was added to ensure that we would not delete a file being written to at the time or removal. We are not removing the base log. Deployments occur as part of workflow.

Gwen