Feature #646
Two connections with same network name
Status: | New | Start: | 11/14/2011 | |
Priority: | High | Due date: | ||
Assigned to: | Mirco Bauer | % Done: | 0% |
|
Category: | Engine | |||
Target version: | - | |||
Complexity: | ||||
Votes: | 1 (View) |
Description
Smuxi currently does not check whether two servers of the same network are connected.
E.g. it is possible to connect with IRCnet twice while both server tabs are named IRCnet. Both servers are using the same log due to that as the log folder is named by the network name.
On connecting Smuxi should check for the existence of another connection with the same network name. Either it should refuse the connection or name the connection tab accordingly.
Related issues
related to Smuxi - Bug #629 | Exception: Exception has been thrown by the target of an invocation. | Rejected | 09/14/2011 | ||
related to Smuxi - Bug #632 | Exception: Exception has been thrown by the target of an invocation. | Rejected | 10/14/2011 | ||
related to Smuxi - Feature #650 | Abort 2nd connection to the same IRC network | New | 11/19/2011 |
History
Updated by Bianca Mix 4784 days ago
This condition is causing the Smuxi server to crash. The network name is used for the logging and both server might access the same log.
As for ticket 632 the exception is having the same symptoms - the server crashed and due to that the database is defraged and a TCP transport error is shown. It was always related to the network IRCnet which was accessed via two servers at the same time (one cause the german server was not reachable and as an interim solution a server in the netherlands was used. One of the channels joined is a german-only channel which required to use the german server again once it is back. During the time of establishing the connection to the german server and closing the server in the netherlands both connections existed in parallel triggering the crash of smuxi server)
This is related to git-version of smuxi only.
Updated by Mirco Bauer 4781 days ago
- Category set to Engine
- Priority changed from Normal to High
- Target version set to 0.8.9
Updated by Mirco Bauer 4745 days ago
- Target version deleted (
0.8.9)
This is no longer a real issue as Smuxi's persistent message buffers deals already with this situation and for plain text logging it does make the log looking a bit odd but is not really causing any issues. On most IRC networks clones are disallowed anyhow.
Updated by Mirco Bauer 4151 days ago
- Assigned to set to Mirco Bauer
- Target version set to 0.10
Updated by Mirco Bauer 4043 days ago
- Target version deleted (
0.10)