wemux command doesn't recognize "rogue"

[binary132]

user@host:~$ wemux rogue
unknown command: rogue
To see a list of wemux commands enter 'wemux help'
user@host:~$ wemux help
wemux version 3.2.0
Current wemux server: wemux

Usage: wemux [command]
To host a wemux server please use one of the following:

    [s]       start: Start the wemux server/attach to an existing wemux server.
    [a]      attach: Attach to an existing wemux server.
    [k]        stop: Kill the wemux server 'wemux', delete its socket.

    [j] join [name]: Join the specified wemux server.
    [j]        join: Display the current wemux server.
    [d]       reset: Join default wemux server: wemux
    [l]        list: List all currently active wemux servers.
    [u]       users: List all users currently attached to 'wemux'
               kick: Disconnect an SSH user, remove their wemux server.

    [c]      config: Open the wemux configuration file in vi.
    [h]        help: Display this screen.
            no args: Start the wemux server/attach to an existing wemux server.
user@host:~$ sudo su -
root@host:~# cd /usr/local/share/wemux/
root@host:/usr/local/share/wemux# ./wemux help
wemux version 3.2.0
Current wemux server: wemux

Usage: wemux [command]
To connect to wemux please use one of the following:

    [m]      mirror: Attach to 'wemux' in read-only mode.
    [p]        pair: Attach to 'wemux' in pair mode, which allows editing.
    [r]       rogue: Attach to 'wemux' in rogue mode, allowing you to pair
                     and also work in other windows independent of the host.
    [o]      logout: Log out of the current wemux rogue session.

    [j] join [name]: Join the specified wemux server.
    [j]        join: Display the current wemux server.
    [d]       reset: Join default wemux server: wemux
    [l]        list: List all currently active wemux servers.
    [u]       users: List all users currently attached to 'wemux'

    [h]        help: Display this screen.
            no args: Attach to 'wemux' in rogue mode.

root@host:/usr/local/share/wemux# ls -la /usr/local/bin/wemux 
lrwxrwxrwx 1 root root 28 Mar 18 13:52 /usr/local/bin/wemux -> /usr/local/share/wemux/wemux

[zolrath]

Mirror/Pair/Rogue are for the guest accounts that ssh into the hosts server depending on the level of access you want to give the guest. Mirror only allows them to see what the host does, Pair keeps them on the same screen as the host but lets them enter text, and Rogue lets them go off into their own tmux tabs independently of the host.

I'm assuming the account you're trying to wemux rogue with is the host so rogue isn't necessary.
Or is this from another account?

[binary132]

Hey! Thanks for the quick pingback. I'm the server admin. I have two coworkers that I want to join a wemux sesh with me. I've made the three of us user accounts on the server.

I can run wemux as my user, and they can join my session by issuing the command wemux from their accounts. It defaults to pair mode. However, when they try to use rogue by entering wemux rogue, it simply responds with unknown command: rogue. I was also unable to get it to work by defaulting it to rogue mode in the config.

Everything is unusually stock, since I just created this server (a ubuntu 13.10 vm.) I followed everything basically to the letter. No clue what comes next.

[zolrath]

Hm sounds like they're all added to host_list in the config? With how wemux is currently set up if you run wemux conf only the hosts account should be in that list.

[binary132]

Yeah, they're all in host_list because I want all of us to be able to initiate the workflow of "hey, something is weird here, ping people in to hop in my new wemux session and get an extra pair of eyes on this."

[binary132]

It looks like it works properly when I remove them from host_list. Is this the intended behavior? Is there any way I can achieve the workflow I'm aiming for?

[zolrath]

I completely forgot that I implemented a solution to this and didn't document it.
You can keep the other users in the host_list if you'd like them to be able to host, but when they need to attach to another hosts session as a client they can type wemux client <command> and wemux will run the command as if they were a regular client.
wemux client rogue will allow a host to rogue into another hosts session.

Time to document it! Hope that helps.

[ijaaz]

You definitely should document it!! I was quite confused till I found this issue.

[jgillman]

👍 Yes! Please document it, I ran into the same problem today and didn't realize what the problem was until I looked through the Issues thinking it was a bug.

[nifr]

Same here - found the solution only by browsing issues over here.

Adding it to the docs would be nice.

[IAmIlliest]

Also same here, only learnt about the client command from here. Definitely worth adding to your docs.

Great program though, very helpful for supporting junior admins and level 1/2 staff etc.

[Foaly]

Yes please document this!
We ran into the same problem and only found the solution after some googeling around. Thanks for the great script though!

[Bendrien]

Yes, updating the docs would be nice!

[likewise]

Still ran into this today. It's not really documented like this.

[minsuu]

Why is this still not documented?!

[danielmkarlsson]

Chiming in here... I also learned about this here so I guess this is still a thing on a toDo.
SuperDuper software tho so, I dunno, I'm complaining when I shouldn't be, I guess.

[completely reverses position after having thought it over]

Thank you, is all I really wanna say. Doing stuff The Man tells you to do is for chumps anyway am I right? You go your own way! It's fine! Never document!