Thanks for your reply, Arfer.arfer wrote:I'm not entirely sure I understand your question but I would make three observations.
1. If you are saying that when you connect to IRC from an alternative computer and find that your bot does not seem to be amongst the IRC channel users, then you are possibly connecting to to a different network server that is split from the one your bot is on.
2. The channel log definition in your .conf file would not generally need a full path for the file it creates to log channel events. It is normally saved to the logs subdirectory of your bot installation. You seem to be saving it to your bots root directory anyway.
3. There seems to be a space missing in the channel log definition in your .conf file unless this was simply an error in pasting the information to this forum.
Taking 2 and 3 above into account, change
logfile jpk #CHANNELNAME"/home/eggdrop/CHANNELNAME.log"
to
logfile jpk #CHANNELNAME "logs/CHANNELNAME.log"
I don't know if this helps or I have completely misunderstood your question.
Thanks for the quick reply.nml375 wrote:Basically, either they're not connected to the same server (or servers on the same irc network), or the irc server(s) are playing a trick on you.
Taking into account the debug output in your first post, your eggdrop sees itself joining a channel where it instantly gains operator privileges, and is the sole channel-member (in essence, it "created" the channel).
Since you say you've got several other clients connected, which can see eachother but not your eggdrop, this only means that your clients and your eggdrop are in fact not joining the same channel. Either the channel-names are messed up, the server-names messed up, or your irc server(s) are playing tricks on you (I don't suppose you're using !channels ?)
The 1st url you give appears to download, compile, make, etc the eggdrop. The 2nd url appears to do the same with added benefit of a simplified (albeit incomplete) eggdrop.conf setup. Using strictly these 2 urls to configure your eggdrop cause this behavior.lxsg wrote:I'm trying to log the conversation on an IRC channel, and I've set up an Eggdrop on my VPS based on these two guides:
http://www.arkinex.com/guides/65/instal ... op-debian/
http://www.cyberarmy.net/library/article/207
..snipped over quoting irrelevant parts, they've been omitted..
Any idea what could have caused this issue?
Code: Select all
# What is your network?
# 0 = EFnet
# 1 = IRCnet
# 2 = Undernet
# 3 = DALnet
# 4 = +e/+I/max-modes 20 Hybrid
# 5 = Others
set net-type 0
I've changed that to "5" after reading through the entire .conf file (thanks to the 2 die statements embedded in there ).speechles wrote:The 1st url you give appears to download, compile, make, etc the eggdrop. The 2nd url appears to do the same with added benefit of a simplified (albeit incomplete) eggdrop.conf setup. Using strictly these 2 urls to configure your eggdrop cause this behavior.lxsg wrote:I'm trying to log the conversation on an IRC channel, and I've set up an Eggdrop on my VPS based on these two guides:
http://www.arkinex.com/guides/65/instal ... op-debian/
http://www.cyberarmy.net/library/article/207
..snipped over quoting irrelevant parts, they've been omitted..
Any idea what could have caused this issue?The default is set to efnet. Simply put, it starts out at 0. Unless you change this to what network-type your connecting to (and neither url above does, hence my mentioning icomplete up there), and it just so happens it isn't efnet. Well, you've just discovered what happens.Code: Select all
# What is your network? # 0 = EFnet # 1 = IRCnet # 2 = Undernet # 3 = DALnet # 4 = +e/+I/max-modes 20 Hybrid # 5 = Others set net-type 0