Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • Could you make this more of a teachable moment by expanding the answer to explain what this does and why it solves the problem? Thanks. from review
    – fixer1234
    Commented Apr 3, 2019 at 14:00
  • Sure. My apology for being too short. I was getting the error mentioned in the post, that it gobbles up disk space like 2.3 GB and I didn't install the binary dump-acct to see the pacct file, which is a binary file. This file contains all the command run by the process, kinda command logging facility. With the help of dump-acct binary, you can clearly see the format, when the command run. All I had to do, get into the dir and fire that command against that file to see the output informative manner. This stuff can be used in security purpose too. Lastly, I can easily nullify it by #>pacct Commented Apr 4, 2019 at 16:07