Feature Request - Capture file Cleanup option for VM

[Pcrossley69]

I recently became aware that my VM was growing because of the number of old packet captures.

I logged into the VM and at the shell prompt I ran:

find /opt/gns3/projects -name *.pcap -exec rm {} ;

And cleared out several Gigabytes of old captures!

This seems a bit brute force and wouldn't be ideal for
I would like a more targetted way of doing this - maybe from the VM menu.
But I would also like to see which projects I am cleaning by name - not ID.

(It might therefore be useful to add a small text file under each project directory in the VM to hold the name of the project.)

[grossmj]

Thanks for your request. Maybe having the option from GNS3 directly is better?

[josephmhiggins]

It is great that you are using wireshark.
I developed a procedure on my GNS3 to only have one project on my gns3 vm - End Project.
Some of my wireshark capture were 100GB..
Wireshark on gns3 is great but so few gns3 user utilize it :(
The introduction of Wireshark into GNS3 was amazing, but the implementation, with respect to filters (for Windows users was poor)............but so few gns3 users utilize wireshark...it is not very effective to optimize it.
The GNS3 developers will be switching from ubridge to a linux bridge sometime in the near future (next 2 years).
Consequently, I have decided not to relearn the programming language C.
My gns3 End Project allows users to:
keep their hard disk usage at a minimal
effortlessly rollback to the previous gns3 version if there is some kind of typo in a new gns3 version (for windows users they have to turn off automatic updates for 7 days and not install any new programs and they need their old projects in a directory called projects-gns3-version-yyy) and a rollback will "NEVER" fail - never being windows updates can destroy anything.

One of my books, says you have to look at scripting opportunities and weigh their cost.
You have a one line command (I used 2 lines in my process to delete old pcap files that takes 2 seconds).

I have been using my commands/your command for over a year.

Your cost to the gns3 develoopers to benefit for gns3 users ratio looks extremely poor.

I would recommend you keep typing your remove command - be that as it is.

My GNS3 End project is the real deal.
The GNS3 developers using linux bridge instead of ubridge is the real deal and we can get proper tcpdump/wireshark filters installed on the gns3 vm.

Please note, I have switched to esxi 7.0 from windows 10 eleven days ago, so it is a little hectic here.