[OPENDJ-2436] OpenDJ: Need a command tools switch to limit /tmp/opendj-*-<date>.log file creation Created: 16/Nov/15  Updated: 08/Nov/19  Resolved: 21/Nov/15

Status: Done
Project: OpenDJ
Component/s: tools
Affects Version/s: 3.0.0, 2.6.3, 2.6.2, 2.6.1, 2.6.0
Fix Version/s: 3.0.0

Type: New Feature Priority: Minor
Reporter: Lee Trujillo Assignee: Ludovic Poitou
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Duplicate
is duplicated by OPENDJ-1805 Disable logging from client tools Done
Relates
relates to OPENDJ-2292 Create setup/uninstall/dsreplication ... Dev backlog
is related to OPENDJ-1052 Exception is logged during dsreplicat... Done
is related to OPENDJ-2622 Setup CLI and GUI handle setup.log fi... Done
Dev Assignee: Ludovic Poitou
Support Ticket IDs:

 Description   

Command line tools that are run as part of setup or monitoring, write a log to /tmp (Unix) or /var/folders/32/XXXXXXXXXXX/T/ (OSX) etc.

If the tool, such as "dsreplication status" or "status" is used on a very frequent basis, the log files can build up, unknown to an administrator. This is very likely in the former case.

The commands

  • setup
  • control-panel
  • status
  • dsreplication status

We should have a command line option to stop these los from being written if desired.

Example: --noToolLog or --noCommandReport etc.



 Comments   
Comment by Chris Ridd [ 17/Nov/15 ]

We have had a customer case (linked) where the filesystem containing these logs (/tmp in their case) ran out of inodes.

Comment by Ludovic Poitou [ 17/Nov/15 ]

I suggest that we remove the temporary log files, whenever the command executed returns success.
This will be more efficient than addition an option.
I would also suggest that if we add an option, it would be to keep the log (--keepTempLogOnSuccess).

Comment by Ludovic Poitou [ 20/Nov/15 ]

So these temp log files are more for debug than anything.
For OpenDJ 3.0, we do close and delete them when the command is successful.
This will be the case for status, dsreplication, control-panel and setup.

Comment by Matthew Swift [ 07/Nov/19 ]

Moved to closed state because the fixVersion has already been released.

Generated at Sat Oct 31 01:29:57 UTC 2020 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.