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
If the username have dots in it, then rogue mode doesn't work (can't find the window).
With a server running, when a user with . in the username (e.g. john.smith) issues wemux rogue, we get the following message:
Can't find window wemux-john
(note how there's no .smith in the window name). A window named john.smith gets created, but wemux can't find it, cause it's only searching for the text before the .
I hacked the following change in /usr/bin/wemux (added the second line to replace . with _ in the username):
and added the corresponding usernames (with _ replacing .) to host_list in /etc/wemux.conf and we could finally get rogue mode to work (pretty nice feature!).
Of course, the hack I present is not a real solution. Ideally, the usernames in /etc/wemux.conf are the real unix usernames. But my bash knowledge is not enough to propose a real patch.
The text was updated successfully, but these errors were encountered:
If the username have dots in it, then rogue mode doesn't work (can't find the window).
With a server running, when a user with
.
in the username (e.g.john.smith
) issueswemux rogue
, we get the following message:(note how there's no
.smith
in the window name). A window namedjohn.smith
gets created, but wemux can't find it, cause it's only searching for the text before the.
I hacked the following change in
/usr/bin/wemux
(added the second line to replace.
with_
in the username):and added the corresponding usernames (with
_
replacing.
) tohost_list
in/etc/wemux.conf
and we could finally get rogue mode to work (pretty nice feature!).Of course, the hack I present is not a real solution. Ideally, the usernames in
/etc/wemux.conf
are the real unix usernames. But my bash knowledge is not enough to propose a real patch.The text was updated successfully, but these errors were encountered: