3 ms·

A lot of talk about what to do yourself, I'd say do nothing yourself. Find an expert who has masses of experience who can consult on it. This isn't a good tim

A lot of talk about what to do yourself, I'd say do nothing yourself. Find an expert who has masses of experience who can consult on it. This isn't a good time to be learning and testing those lessons.

faeyanpiraat 7y ago
This is the solution in my experience aswell. Doing even minor things that could distrupt the execution for any time (attaching debugger, installing packet sniffer that blocks network traffic for a sec or cause a packet lost, etc) could deadlock the application. Wouldn’t risk it.
- jmkni 7y ago
  The only thing I would risk is copy/pasting the binary/executable that is running to somewhere else so I could try and decompile it. Anything beyond that is a nope.
alexandercrohde 7y ago
Yes. Moreover, if you backup the system great, you get peace of mind, but management hardly cares. If you BREAK the system while trying to establish a backup, management cares and it's "your fault." You have exponentially more to lose than to gain by experimenting with this at all. In this situation you should convey the risks, let the stakeholders decide if/who is going to address this, as it's their risk to take.