magnumjec

ZNC multiclients

Jan 17th, 2020 (edited)
539
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.06 KB | None | 0 0
  1. znc > 1.6.0
  2.  
  3. $zncuser = your znc user
  4.  
  5. Load route_replies for every network for every user (and consequently load it for any networks created after this point)
  6. - On each network: /msg *status loadmod route_replies
  7.  
  8. Per https://wiki.znc.in/Clientbuffer#Configuration you want to disable AutoClearChanBuffer and AutoClearQueryBuffer
  9. - On each user:
  10. - /msg *status loadmod controlpanel
  11. - /msg *controlpanel set AutoClearChanBuffer $zncuser false
  12. - /msg *controlpanel set AutoClearQueryBuffer $zncuser false
  13.  
  14. Build the latest/patched clientbuffer module, assuming your ZNC path is ~/.znc, update as necessary. You also need znc-buildmod,
  15. what package that is in depends on your distro (commonly znc-dev or znc-devel). If you compiled ZNC from source, you already have
  16. znc-buildmod:
  17. - mkdir ~/.znc/modules ; cd ~/.znc/modules
  18. - git clone https://github.com/CyberShadow/znc-clientbuffer.git
  19. - cd znc-clientbuffer
  20. - znc-buildmod clientbuffer.cpp
  21. - cp clientbuffer.so ..
  22.  
  23. Load the clientbuffer module
  24. - On each network:
  25. - /msg *status loadmod clientbuffer autoadd
  26. (the 'autoadd' argument negates the need for you to manually '/msg *clientbuffer addclient <clientid>' for each client)
  27.  
  28. Make sure your IRC clients all login with a client identifier
  29. - See https://wiki.znc.in/Clientbuffer#Identifiers and https://wiki.znc.in/ZNC and look for "clientid", ie: username@CLIENTID/network
  30. - Each clientid you want to have unique history must be a unique name
  31. - You will need to put a clientid on every client, if you do not on a client the behavior is (TBD)
  32. - Verify that each clientid is received/identified in *clientbuffer with /msg *clientbuffer listclients
  33. (each specified clientid should appear in the list, if it doesn't, then your client configuration needs fixing)
  34.  
  35. And make sure your config is saved
  36. - /msg *status saveconfig
  37.  
  38. Optional/related info:
  39. - Set up Playback module
  40. - Chanfilter might also be of interest for mobile users
  41. - Backlog is also useful to request additional logs, requires the Log module having logged the data first
Add Comment
Please, Sign In to add comment