Node:Muhrc Commands, Previous:Muh Commands, Up:Top

Muhrc Commands

There are numerous commands with which you can extensively customize Muh's behaviour. They must be placed in the muhrc that muh reads on startup, it is usually $HOME/.muh/muhrc.

Required settings

nickname <string>: The nickname muh will use on IRC. If it is occupied it will switch to the alternate nickname and will periodically attempt to get that nick.
altnickname <string>: Alternative nickname if nickname configured with nickname is occupied. If this one is occupied as well muh will use a random nickname.
realname <string>: Your name on IRC as shown by the /WHOIS-command.
username <string>: Your Unix-username. If there is no identd running on your site this username will be used.
listenport <int>: This is the port on which Muh will wait for connects: Use this as the port to connect to in your IRC-Client.
password <string>: This is the password that protects your Muh-session. If it is exactly 13 characters in length Muh assumes it is crypted. Try muh -c to get a crypted version of your password.
servers <serverlist>: Put all of Muh's IRC-Servers here. It will cycle through the list.

Optional settings

logging <boolean>: true: Log messages that other users send you while you are not connected?
leave <boolean>: true: Leave all the channels you're in when you disconnect your IRC-client from Muh?
leavemsg <string>: empty: This string will be sent as an action to all the channels you're in when you disconnect your client.
away <string>: empty: If you're not connected people messaging you will receive this string once.
getnick <boolean>: true: Attempt to get the nickname specified with nick if occupied?
nevergiveup <boolean>: false: If set then Muh will never stop trying to connect to a server, otherwise it will terminate if there is no functional IRC-server left.
rejoin <boolean>: false: Rejoin the channels Muh was in after changing IRC-server?
bind <hostname>: none: Bind to another IP than the default? This is commonly referred as the VHOST. (todo: ipv6)
antiidle <boolean>: false: If set then the IRC-idle-time will get reset every ten minutes by sending a dummy-message.
norestricted <boolean>: false: Muh won't tolerate a restricted (+r) connection. If a connection gets restricted Muh will jump to the next IRC-server available.
forwardmsg <string>: none: If set Muh will collect the messages it has received within 3 minutes and pipe them to the program specified here.
hosts <permissionlist>: all allowed: List the hosts that are allowed to connect to Muh here. Notice that the default-match is always true so you need to explicitly forbid all other hosts at the very end of your list. Muh always tries to match both the IP and the hostname.
people <permissionlist>: all allowed: List the people (IRC-hostmask style) that are allowed to send you private messages. Default-match is always true.
dccbounce <boolean>: false: Also bounce all DCC's? Keep in mind that if you send/receive files that the data will go through the site Muh is running on. MIRC-Style resumes work as well.
dccbindclient <string>: empty: Bind passive DCC's to another IP than the default. This is usually only needed in delicate network-environments and you'll definitely know when this is required.
logfull <boolean>: false: Log all channel-, server- and private traffic to log files? This might get you many big files - but you have something to read when everybody else is idle.
logfilenametemplate <string>: empty: obsolete?
logtimestamptemplate <string>: [%a %d %b %H:%M:%S]: obsolete?