4

Note to self: keep not trusting online tutorials and ALWAYS, A.L.W.A.Y.S take them with a grain of salt.

Now why do you fine lads think `nmcli networking off && nmcli networking on` over ssh is a bad idea? And how to quickly make it suitable for over-ssh-execution? Let's see who knows shell! [HINT: see tags for an almost-answer]

... when people not sure what shell characters mean are writing tutorials... FUCK!

Comments
  • 2
    Id be too paranoid, but I offer an alternative, put the re-activation command on a 1 minute cron xD
  • 1
    I'd say fucking with network when you want ssh to work always goes south.
  • 1
    @kescherRant @m1sf3t @stonestorm

    for starters it would be nice to join both commands with unconditional execution: replace && with a ; . Joining them with && while the second one is the most important for you is like Fort Knox building indefeatable walls and not minding about the gate.
  • 2
    @netikras Yes, but to be safe, I'd rather just not execute those commands if I don't have any other way of accessing a system. What if the second command fails for some reason anyway? Can't debug the issue without access.
  • 0
    @kescherRant sometimes you just don't have any other access :)
  • 0
    I'd probably just wrap the command in zsh -c "command" $! to run and disown it.
  • 0
    @PrivateGER can zsh reattach to a disowned process? I prefer screen or tmux for that
  • 0
    @netikras Isn't nmcli just a tiny network command? Why would you reattach?
  • 0
    @M1sf3t alright captain Barbosa
  • 0
    @PrivateGER To see what was the error (if any)
  • 1
    @M1sf3t aaahh, so THAT's where I've heard that phrase :D Nice!

    Now I feel the urge to watch the whole saga again

    EDIT: YESS!! They have it on Netflix!
  • 0
    @M1sf3t Ya best start believing in ghost threads, mrs. turner. You're in one!
Add Comment