Clearing log, connect/disconnect

[ZanyScum]

When I just delete everything, there will only be one "disconnect" log entry for my IP without a matching "connect" entry.
Everyone in RL will know that something fishy has been done.

Does the game recognize this as a problem? Do I have to leave matching connect/disconnect entries?

[Nova Solarius]

The DLC will comment on it, but I don't think it causes issues. You can always use forkbomb to disconnect without leaving logs.

[ZanyScum]

Ok, thank you. I will continue with "rm *" for now. Even if it leaves a bad taste in my mouth. I think in Uplink you were busted if you did it like this.

forkbomb will remove the logs? That is news to me. Thanks.

[Nova Solarius]

Forkbomb will not so much remove the logs as not leave a disconnect log because the machine shuts down before you disconnect.

[ZanyScum]

Originally posted by Nova Solarius:

Forkbomb will not so much remove the logs as not leave a disconnect log because the machine shuts down before you disconnect.

Oh, that makes now so much more sense to me. Thank you! I think I will consider this option from now on.

[FordGT90Concept]

forkbomb leaves a kernel panic error. Can't use this on shell computers though because it would kill the shell. Forkbombed computers come back after 30 seconds.

When you get hacked and are forced to reboot, you're being forkbombed. If you're inhumanly fast, you can "ps" then "kill <id>" of the forkbomb. You can also forkbomb yourself if you want to see how it works.

[Nova Solarius]

Originally posted by FordGT90Concept:

forkbomb leaves a kernel panic error. Can't use this on shell computers though because it would kill the shell. Forkbombed computers come back after 30 seconds.

When you get hacked and are forced to reboot, you're being forkbombed. If you're inhumanly fast, you can "ps" then "kill <id>" of the forkbomb. You can also forkbomb yourself if you want to see how it works.

This is pretty much how it works, yeah. Kernel panic errors don't store IPs and are untraceable as a result.

And a second option to prevent forkbombing beyond killing the process is to use a shell trap.

[ZanyScum]

Originally posted by Nova Solarius:

And a second option to prevent forkbombing beyond killing the process is to use a shell trap.

I read about that but don't get it. I always have two shells open, one with a trap and one so I can disable proxies.
The one with the trap I just don't get. There is that "Trigger" text, and then? Could you explain it using small words?

[Nova Solarius]

Originally posted by ZanyScum:

Originally posted by Nova Solarius:

And a second option to prevent forkbombing beyond killing the process is to use a shell trap.

I read about that but don't get it. I always have two shells open, one with a trap and one so I can disable proxies.
The one with the trap I just don't get. There is that "Trigger" text, and then? Could you explain it using small words?

You click the trigger to shut down your system before the hacker can cause damage.

[ZanyScum]

arggg, "click the trigger".
I thought I would sometime learn to somehow connect the "trigger" with a "shutdown" or something.
It never even occurred to me to click a "trigger" :-) Thank you.