You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GNS3 users that use the GNS3 VM get destroyed when something bad happens to the GNS3 VM - for whatever reason.
The primary culprit is that they are not "ending" their project by exporting it.
This is not explicitly taught anywhere.
There are several implementations in export_project.py that I consider sub-standard (not enough log messages are written out).
I will "end" all my projects.
It will take make about 10 days to do it because I have to "fill out the paperwork" and make sure I have things like a "topology.png", a proper accounting of my "log" files.
The "log" files will be tricky because export_project.py refuses to export them - which looks like a good design to me.
The "capture" files will be tricky because export_project.py refuses to export them - which looks like a good design to me.
GNS3 users do not like to reveal their username (and I am actively engaged in finding the RFC that says you should not reveal your username, but I can not find the RFC that says people should not reveal their username), so this message:
Error while closing project 1f9cabd3-9c0d-428b-96be-c09efc7a86a4: Project 'AlmaLinux' cannot be deleted because it is not in the default project directory: 'C:\Users\joe_I7\GNS3\projects'
looks to be an illegal design. Although, I will have to wait until I can find the RFC for conclusive direction,
Ummm.....'AlmaLinux' cannot be deleted because it is not in the default project directory.....
I do not know what to make of it at this time. At this time, i have a
projects\vmware
projects\virtualbox
I moved yesterday on C:\Users\joe_I7 and I used Replace in my code to strip out powershell $HOME in my log messages - which only I can see.
The linux way of ~/ looks better to me.
GNS3 users do not like revealing their username.
However, GNS3 users do not like revealing their hostname.
Unfortunately, I know of no such RFC that says you can not promulgate your hostname.
So...yeah...I suggest the username be stripped from all log messages done by GNS3.
That's just what GNS3 users want.
The text was updated successfully, but these errors were encountered:
GNS3 users that use the GNS3 VM get destroyed when something bad happens to the GNS3 VM - for whatever reason.
The primary culprit is that they are not "ending" their project by exporting it.
This is not explicitly taught anywhere.
There are several implementations in export_project.py that I consider sub-standard (not enough log messages are written out).
I will "end" all my projects.
It will take make about 10 days to do it because I have to "fill out the paperwork" and make sure I have things like a "topology.png", a proper accounting of my "log" files.
The "log" files will be tricky because export_project.py refuses to export them - which looks like a good design to me.
The "capture" files will be tricky because export_project.py refuses to export them - which looks like a good design to me.
GNS3 users do not like to reveal their username (and I am actively engaged in finding the RFC that says you should not reveal your username, but I can not find the RFC that says people should not reveal their username), so this message:
Error while closing project 1f9cabd3-9c0d-428b-96be-c09efc7a86a4: Project 'AlmaLinux' cannot be deleted because it is not in the default project directory: 'C:\Users\joe_I7\GNS3\projects'
I do not know what to make of it at this time. At this time, i have a
projects\vmware
projects\virtualbox
I moved yesterday on C:\Users\joe_I7 and I used Replace in my code to strip out powershell $HOME in my log messages - which only I can see.
The linux way of ~/ looks better to me.
GNS3 users do not like revealing their username.
However, GNS3 users do not like revealing their hostname.
Unfortunately, I know of no such RFC that says you can not promulgate your hostname.
So...yeah...I suggest the username be stripped from all log messages done by GNS3.
That's just what GNS3 users want.
The text was updated successfully, but these errors were encountered: