Language:
switch to room list switch to menu My folders
Go to page: First ... 36 37 38 39 [40] 41 42 43 44 ... Last
[#] Thu Feb 26 2015 15:28:18 EST from jefft88 @ Uncensored

Subject: secure authentication with Citadel.

[Reply] [ReplyQuoted] [Headers] [Print]

Hello,

Does anyone know how to set up secure authentication with Citadel.

Thanks,

Jeff



[#] Thu Feb 26 2015 17:06:35 EST from IGnatius T Foobar @ Uncensored

Subject: Re: secure authentication with Citadel.

[Reply] [ReplyQuoted] [Headers] [Print]

Does anyone know how to set up secure authentication with Citadel.

Yes, many people do.

[#] Sat Feb 28 2015 03:59:54 EST from mo @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

 

 

Sun Feb 15 2015 20:44:18 EST from IGnatius T Foobar @ Uncensored

Hi everyone.

This morning I made some small but *very* effective bugfixes to the XMPP service in Citadel. These changes are *live* here on Uncensored. So far, I have tested the following clients:

* Pidgin (of course)
* jwchat.org (a web-based client ... not sure why you'd use this in production since WebCit has a chat client built in, but it tested clean and that's good)
* Xabber (a client for Android)

All three are working great now. So here's where you come in, folks ... if you have any other favorite clients, now's the time to test them. Again, test them here on Uncensored, not on a released version of Citadel, as we haven't published this code yet. I suppose you could also test against git master if you really insist on your own server.

Here are the tests that need to be run:

1. When you log in, the roster should populate with all other users who are logged in.
2. Send and receive instant messages (of course).
3. When users log in and out, they appear and disappear from the roster.
4. The roster of a Citadel account should *never* show any "offline buddies."
This is because Citadel's XMPP implementation assumes that the user community should always consist of the people currently logged in to the server, and sends roster pushes to reflect this.

If you test a client and the above four tests pass, please post your results so we can include that client in the next release announcement.

I just logged in to uncensored xmpp/jabber with the "bitlbee"  (IRC to xmpp gateway) client. This is for users of the "irssi" IRC client, which i know at least one of you here uses, and means you can access all xmpp chat rooms while using IRC (on colsole).

Here is how i set it up:

 

1) Install bitlbee:        I used my linux distros package manager 

2) connect  to bitlbee deamon:     start the  IRC client, irssi;-  

  •  issue:  /connect bitlbee  (or /connect localhost  even:   you should now be in the bitlbee control channel)

3) setup/register an account password for your new bitlbee account** on your machine:

  •   issue: register
  •  issue: /oper
  •  issue: <your-new-bitlbee-account_password>

4) add a xmpp/jabber account:-  

  • issue:   account add  jabber  <username>@uncensored.citadel.org
  • issue: /oper <return>
  • issue: <your-uncensored-account_password>

to check the account has been added successfully:

  • issue: account list

you can add further accounts; twitter, gtalk, facebook etc...

 ** When you come to start up the irssi client next, you will be prompted for your bitlbee password; when you login you will automatically login to 'all' your xmpp/jabber accounts

5) login and chat:  use either the numeric or name ID of the account (you can see the numeric ID when you 'list' the accounts):-

  • issue: account <ID> on     (logout is: account <ID> off, if needed)

You should now see the names of,all your account's, contacts in the bitlbee control channel

to chat with someone in the bitlbee control channel:

  • issue: <contact_name>: <message>    (don't forget the colon after contact's name ;) )

or, which i find 'much' easier if there are alot of people from various xmpp accounts added and 'lot' of contacts in the bitlbee controlo channel:

  • issue: /msg <contact_name> <message>      (and a separate channel will be opened for you and your contact - much easier)

 

 

Now that was to test. To set up so you auto login each time see irssi docs and use same setup for bitlbee as they use for facebook.

 

 

 

 

    

 



[#] Sat Feb 28 2015 04:36:24 EST from mo @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

Bitlbee and irssi, more info:

1)

Here is a link to the bitlbee facebook howto.

https://wiki.bitlbee.org/HowtoFacebook

I used the old way to login, with a password, you might want to use OAuth.

 

2)

and also here is the docs i used, which might be better. I posted them up on my blog on uncensored. See the comments for the docs.

http://uncensored.citadel.org/readfwd?go=trinkets%20and%20oddities?p=1883055487



[#] Sat Feb 28 2015 04:49:08 EST from mo @ Uncensored

Subject: xmpp bitlbee-irssi

[Reply] [ReplyQuoted] [Headers] [Print]

On first impressions, it all works great! I logged in to uncensored with my console iorc client irssi. I saw all 'most' of the logged in users on uncensored - but not all?

I left a message for someone and had a chat with them. Great!

I was logged on to webcit at the same time as using my console irc client and the webcit chat/xmpp window opened up as soon as my chat was responded to (via my friends android client - pidgin i believe(?)).

I could see all the messages typed from my friend on both my webcit and irc client. However the two clients i used do not sync ( i typed some messages in my irc client, some on webcit and they were both seen by my friend (on his android client) but i could not see what i typed from webcit on my irc client and the also the other way ) - so you need use one or the other clients to see 'all' your messages in one window.

Still it works like a charm.

 

See my previous post here (no Subject) for a few links to Docs.

Sat Feb 28 2015 03:59:54 EST from mo @ Uncensored

 

 

Sun Feb 15 2015 20:44:18 EST from IGnatius T Foobar @ Uncensored

Hi everyone.

This morning I made some small but *very* effective bugfixes to the XMPP service in Citadel. These changes are *live* here on Uncensored. So far, I have tested the following clients:

* Pidgin (of course)
* jwchat.org (a web-based client ... not sure why you'd use this in production since WebCit has a chat client built in, but it tested clean and that's good)
* Xabber (a client for Android)

All three are working great now. So here's where you come in, folks ... if you have any other favorite clients, now's the time to test them. Again, test them here on Uncensored, not on a released version of Citadel, as we haven't published this code yet. I suppose you could also test against git master if you really insist on your own server.

Here are the tests that need to be run:

1. When you log in, the roster should populate with all other users who are logged in.
2. Send and receive instant messages (of course).
3. When users log in and out, they appear and disappear from the roster.
4. The roster of a Citadel account should *never* show any "offline buddies."
This is because Citadel's XMPP implementation assumes that the user community should always consist of the people currently logged in to the server, and sends roster pushes to reflect this.

If you test a client and the above four tests pass, please post your results so we can include that client in the next release announcement.

I just logged in to uncensored xmpp/jabber with the "bitlbee"  (IRC to xmpp gateway) client. This is for users of the "irssi" IRC client, which i know at least one of you here uses, and means you can access all xmpp chat rooms while using IRC (on colsole).

Here is how i set it up:

 

1) Install bitlbee:        I used my linux distros package manager 

2) connect  to bitlbee deamon:     start the  IRC client, irssi;-  

  •  issue:  /connect bitlbee  (or /connect localhost  even:   you should now be in the bitlbee control channel)

3) setup/register an account password for your new bitlbee account** on your machine:

  •   issue: register
  •  issue: /oper
  •  issue: <your-new-bitlbee-account_password>

4) add a xmpp/jabber account:-  

  • issue:   account add  jabber  <username>@uncensored.citadel.org
  • issue: /oper <return>
  • issue: <your-uncensored-account_password>

to check the account has been added successfully:

  • issue: account list

you can add further accounts; twitter, gtalk, facebook etc...

 ** When you come to start up the irssi client next, you will be prompted for your bitlbee password; when you login you will automatically login to 'all' your xmpp/jabber accounts

5) login and chat:  use either the numeric or name ID of the account (you can see the numeric ID when you 'list' the accounts):-

  • issue: account <ID> on     (logout is: account <ID> off, if needed)

You should now see the names of,all your account's, contacts in the bitlbee control channel

to chat with someone in the bitlbee control channel:

  • issue: <contact_name>: <message>    (don't forget the colon after contact's name ;) )

or, which i find 'much' easier if there are alot of people from various xmpp accounts added and 'lot' of contacts in the bitlbee controlo channel:

  • issue: /msg <contact_name> <message>      (and a separate channel will be opened for you and your contact - much easier)

 

 

Now that was to test. To set up so you auto login each time see irssi docs and use same setup for bitlbee as they use for facebook.

 

 

 

 

    

 



 



[#] Sat Feb 28 2015 04:51:40 EST from mo @ Uncensored

Subject: Re: xmpp bitlbee-irssi

[Reply] [ReplyQuoted] [Headers] [Print]

Just in case it gets missed, this is how i succesfully tested the irssi with bitlbee xmpp client on console:

 

I just logged in to uncensored xmpp/jabber with the "bitlbee"  (IRC to xmpp gateway) client. This is for users of the "irssi" IRC client, which i know at least one of you here uses, and means you can access all xmpp chat rooms while using IRC (on colsole).

Here is how i set it up:

 

1) Install bitlbee:        I used my linux distros package manager 

2) connect  to bitlbee deamon:     start the  IRC client, irssi;-  

  •  issue:  /connect bitlbee  (or /connect localhost  even:   you should now be in the bitlbee control channel)

3) setup/register an account password for your new bitlbee account** on your machine:

  •   issue: register
  •  issue: /oper
  •  issue: <your-new-bitlbee-account_password>

4) add a xmpp/jabber account:-  

  • issue:   account add  jabber  <username>@uncensored.citadel.org
  • issue: /oper <return>
  • issue: <your-uncensored-account_password>

to check the account has been added successfully:

  • issue: account list

you can add further accounts; twitter, gtalk, facebook etc...

 ** When you come to start up the irssi client next, you will be prompted for your bitlbee password; when you login you will automatically login to 'all' your xmpp/jabber accounts

5) login and chat:  use either the numeric or name ID of the account (you can see the numeric ID when you 'list' the accounts):-

  • issue: account <ID> on     (logout is: account <ID> off, if needed)

You should now see the names of,all your account's, contacts in the bitlbee control channel

to chat with someone in the bitlbee control channel:

  • issue: <contact_name>: <message>    (don't forget the colon after contact's name ;) )

or, which i find 'much' easier if there are alot of people from various xmpp accounts added and 'lot' of contacts in the bitlbee controlo channel:

  • issue: /msg <contact_name> <message>      (and a separate channel will be opened for you and your contact - much easier)

 

 

Now that was to test. To set up so you auto login each time see irssi docs and use same setup for bitlbee as they use for facebook.

 

 

 

 

    

 



 



 



[#] Sat Feb 28 2015 05:07:45 EST from mo @ Uncensored

Subject: Re: xmpp bitlbee-irssi

[Reply] [ReplyQuoted] [Headers] [Print]

To add: although i cannot see 'all' of what i typed when alternating between two clients, i 'can' see the full log/conversation in the "sent/recieved pages" room/page on uncensored, so that's great.

Not a great issue if you only chat on one client at a time ;)

 

Sat Feb 28 2015 04:49:08 EST from mo @ Uncensored Subject: xmpp bitlbee-irssi

On first impressions, it all works great! I logged in to uncensored with my console iorc client irssi. I saw all 'most' of the logged in users on uncensored - but not all?

I left a message for someone and had a chat with them. Great!

I was logged on to webcit at the same time as using my console irc client and the webcit chat/xmpp window opened up as soon as my chat was responded to (via my friends android client - pidgin i believe(?)).

I could see all the messages typed from my friend on both my webcit and irc client. However the two clients i used do not sync ( i typed some messages in my irc client, some on webcit and they were both seen by my friend (on his android client) but i could not see what i typed from webcit on my irc client and the also the other way ) - so you need use one or the other clients to see 'all' your messages in one window.

Still it works like a charm.

 



[#] Mon Mar 02 2015 14:58:22 EST from keithalert @ Uncensored

Subject: Server stops responding

[Reply] [ReplyQuoted] [Headers] [Print]

[#] Mon Mar 02 2015 16:21:42 EST from Freejack @ Uncensored

Subject: Attempt to update Citadel/Webcit using Easy Installer......

[Reply] [ReplyQuoted] [Headers] [Print]

I run this and it says there are no updates, I have 8.24, I notice that here it is 8.29 and 8.30. I used the Easy Installer  sudo wget -q -O - http://easyinstall.citadel.org/install | sh .

Am I doing something wrong or is this not been updated?



[#] Mon Mar 02 2015 16:24:11 EST from kirik9 @ Uncensored

Subject: Does Citadel auto refresh for incoming mail

[Reply] [ReplyQuoted] [Headers] [Print]

Hi all,

I am new to citadel so i apologize if this has been asked / answered before.

When a user is on the web interface for citadel, does the inbox auto refresh to show newly arrived email messages?

Thanks,

K.



[#] Mon Mar 02 2015 16:38:51 EST from dothebart @ Uncensored

Subject: Re: Does Citadel auto refresh for incoming mail

[Reply] [ReplyQuoted] [Headers] [Print]

No, currently only instant messages are polled from the server.



[#] Tue Mar 03 2015 10:23:37 EST from TaMeR @ Uncensored to Citadel Support <citadel_support@citadel.org>

Subject: Re: Server stops responding

[Reply] [ReplyQuoted] [Headers] [Print]

On 03/02/2015 09:58 PM, keithalert wrote:

When connecting to WebCit, the message "This program was unable to
connect or stay connected to the Citadel server. Please report this
problem to your system administrator" appears.

I keep getting this after server runs for about 5 min then I need to
reboot and Ideas


Reboot what? The server ???

Check your syslog

[#] Tue Mar 03 2015 12:00:28 EST from keithalert @ Uncensored

Subject: Re: Server stops responding

[Reply] [ReplyQuoted] [Headers] [Print]

Restart the Citserver

it stops and in the log it says shutting down to prevent data loss.

Appears the Database is corrupted and when I try to do a repair it completes by then no accounts work at all. so I bring back the backup and it starts working again.

 



[#] Wed Mar 04 2015 16:42:23 EST from TaMeR @ Uncensored to Citadel Support <citadel_support@citadel.org>

Subject: Re: Server stops responding

[Reply] [ReplyQuoted] [Headers] [Print]

On 03/03/2015 07:00 PM, keithalert wrote:
Restart the Citserver

it stops and in the log it says shutting down to prevent data loss.

Appears the Database is corrupted and when I try to do a repair it
completes by then no accounts work at all. so I bring back the backup
and it starts working again.




We really need more info to understand what is going on.
What comes to mind is, is it possible that you have disk error occurring?

[#] Thu Mar 05 2015 17:27:00 EST from "Motty Cruz" <motty.cruz@gmail.com> to citadel_support@citadel.org

Subject: Citadel Amavisd-new Spamassassin

[Reply] [ReplyQuoted] [Headers] [Print]

Hello,

I just install Citadel-suite amavisd-new Spamassassin, I enable
spamassassin, but I don't see score bayes score being added to incoming
emails. can someone point to a "howto" configure amavisd-new
spamassassin with Citadel?

Thanks in advance,
MOtty

[#] Sat Mar 07 2015 03:20:22 EST from HEATHER RAFFAELLA Riverso @ Uncensored

Subject: Installing citadel with openacs info

[Reply] [ReplyQuoted] [Headers] [Print]

Hello,

I had a question, I would like to use openacs http://www.openacs.net/ as cms, news portal and then use citadel as social networking website,

my question is then, should I instal openacs in a different physical server and instal citadel in a seperated physical server as well or can I isntal both on the same cpanel or webmin hosting control panel?

Be informed that openacs is written in Tcl/Tk programming language and uses aolserver as webserver,

could citadel work with aol server?



[#] Sat Mar 07 2015 04:03:52 EST from "heather" <heather@trans-world.org> to citadel_support@citadel.org

Subject: Fwd: nstalling citadel with openacs info

[Reply] [ReplyQuoted] [Headers] [Print]

Hello,

I had a question, I would like to use openacs http://www.openacs.net/ as
cms, news portal and then use citadel as social networking website,

my question is then, should I instal openacs in a different physical
server and instal citadel in a seperated physical server as well or can
I isntal both on the same cpanel or webmin hosting control panel?

Be informed that openacs is written in Tcl/Tk programming language and
uses aolserver as webserver,

could citadel work with aol server?

[#] Sat Mar 07 2015 04:39:16 EST from "heather" <heather@trans-world.org> to citadel_support@citadel.org

Subject: citadel installation with webmin/virtualmin info

[Reply] [ReplyQuoted] [Headers] [Print]

Hello, in order to manage citadel server should I instal citadel on
webmin/virtualmin or does citadel has a backend server managment admin
with all the linux distros paquage manager and don't need any hosting
control panel at all???

[#] Sat Mar 07 2015 06:24:16 EST from dworz @ Uncensored

Subject: citserver core dump in libev

[Reply] [ReplyQuoted] [Headers] [Print]

hi

Yestarday my citserver started dumping core and brought my server to halt. Could anyone help me fix this?

Is it a problem with the SMTP Queue being to large? If so how can i remove messages manually?

Also the database is pretty large. I tried to dump and load it, but it failed when the dump became almost 4GB in size.

# /usr/sbin/citserver
citserver[29067]: *** Citadel server engine v8.24 (build 5644ab7) ***
[..]
citserver[29067]: SMTPCQ: SMTP Queue: skipping because of num jobs 500 + 50 > 500 max_sessions_for_outbound_smtp
citserver: ev.c:3646: ev_io_start: Assertion `("libev: ev_io_start called with corrupted watcher", ((WL)w)->next != (WL)w)' failed.
citserver[29067]: SMTPCQ: SMTP Queue: skipping because of num jobs 500 + 14 > 500 max_sessions_for_outbound_smtp
Aborted (core dumped)

# coredumpctl -1 info
           PID: 29067 (citserver)
           UID: 993 (citadel)
           GID: 992 (citadel)
        Signal: 6 (ABRT)
     Timestamp: Sam 2015-03-07 11:56:02 CET (12min ago)
  Command Line: /usr/sbin/citserver -D -lmail
    Executable: /usr/sbin/citserver
 Control Group: /user.slice/user-0.slice/session-1.scope
          Unit: session-1.scope
         Slice: user-0.slice
       Session: 1
     Owner UID: 0 (root)
       Message: Process 29067 (citserver) of user 993 dumped core.
               
                Stack trace of thread 29068:
                #0  0x00007fa2344c18d7 raise (libc.so.6)
                #1  0x00007fa2344c353a abort (libc.so.6)
                #2  0x00007fa2344ba47d __assert_fail_base (libc.so.6)
                #3  0x00007fa2344ba532 __assert_fail (libc.so.6)
                #4  0x00007fa236513aa9 ev_io_start (libev.so.4)
                #5  0x00007fa2371f503b SockStateCb (citserver)
                #6  0x00007fa235fff368 ares__send_query (libcares.so.2)
                #7  0x00007fa235fffab8 process_answer.part.1 (libcares.so.2)
                #8  0x00007fa235fffde2 read_udp_packets (libcares.so.2)
                #9  0x00007fa235fffec0 processfds (libcares.so.2)
                #10 0x00007fa2365124e3 ev_invoke_pending (libev.so.4)
                #11 0x00007fa236515b0e ev_run (libev.so.4)
                #12 0x00007fa2371fdd63 client_event_thread (citserver)
                #13 0x00007fa2371f0508 CTC_backend (citserver)
                #14 0x00007fa235bbc52a start_thread (libpthread.so.0)
                #15 0x00007fa23458d22d __clone (libc.so.6)
               
                Stack trace of thread 29069:
                #0  0x00007fa23458d833 epoll_wait (libc.so.6)
                #1  0x00007fa236512e65 epoll_poll (libev.so.4)
                #2  0x00007fa236515405 ev_run (libev.so.4)
                #3  0x00007fa2371fd2c9 db_event_thread (citserver)
                #4  0x00007fa2371f0508 CTC_backend (citserver)
                #5  0x00007fa235bbc52a start_thread (libpthread.so.0)
                #6  0x00007fa23458d22d __clone (libc.so.6)
               
                Stack trace of thread 29070:
                #0  0x00007fa234583ae3 __select (libc.so.6)
                #1  0x00007fa2371d1ba4 worker_thread (citserver)
                #2  0x00007fa2371f0508 CTC_backend (citserver)
                #3  0x00007fa235bbc52a start_thread (libpthread.so.0)
                #4  0x00007fa23458d22d __clone (libc.so.6)
               
                Stack trace of thread 29067:
                #0  0x00007fa2345511bd __nanosleep (libc.so.6)
                #1  0x00007fa234584224 usleep (libc.so.6)
                #2  0x00007fa2371f071a go_threading (citserver)
                #3  0x00007fa2371c538e main (citserver)
                #4  0x00007fa2344acfe0 __libc_start_main (libc.so.6)
                #5  0x00007fa2371c562c _start (citserver)
               
                Stack trace of thread 29071:
                #0  0x00007fa23450dc16 _int_malloc (libc.so.6)
                #1  0x00007fa23451015e malloc (libc.so.6)
                #2  0x00007fa235ddcc35 InsertHashItem (libcitadel.so.4)
                #3  0x00007fa235ddd46f Put (libcitadel.so.4)
                #4  0x00007fa23722fa65 QItem_Handle_Recipient (citserver)
                #5  0x00007fa23722f581 DeserializeQueueItem (citserver)
                #6  0x00007fa23723076d smtp_do_procmsg (citserver)
                #7  0x00007fa2371e4ecc CtdlForEachMessage (citserver)
                #8  0x00007fa23722ee9b smtp_do_queue (citserver)
                #9  0x00007fa2371d4405 PerformSessionHooks (citserver)
                #10 0x00007fa2371ec0ec do_housekeeping (citserver)
                #11 0x00007fa2371d1cf5 worker_thread (citserver)
                #12 0x00007fa2371f0508 CTC_backend (citserver)
                #13 0x00007fa235bbc52a start_thread (libpthread.so.0)
                #14 0x00007fa23458d22d __clone (libc.so.6)

# rpm -q citadel citadel-common libcitadel4 citadel-lang webcit webcit-lang libsieve1
citadel-8.24-7.1.x86_64
citadel-common-8.24-7.1.x86_64
libcitadel4-8.24-1.1.x86_64
citadel-lang-8.24-7.1.x86_64
webcit-8.24-7.1.x86_64
webcit-lang-8.24-7.1.x86_64
libsieve1-2.3.1-1.1.x86_64

# cat /etc/redhat-release
Fedora release 21 (Twenty One)

# uname -a
Linux base.amazing.ch 3.18.7-200.fc21.x86_64 #1 SMP Wed Feb 11 21:53:17 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

# ls -l /var/lib/citadel/data/
total 3265520
-rw-------. 1 citadel root      52334592  7. Mär 11:54 cdb.00
-rw-------. 1 citadel root          8192  7. Mär 11:54 cdb.01
-rw-------. 1 citadel root         69632  7. Mär 12:18 cdb.02
-rw-------. 1 citadel root         16384  7. Mär 12:18 cdb.03
-rw-------. 1 citadel root        389120  7. Mär 11:54 cdb.04
-rw-------. 1 citadel root         53248  6. Mär 22:17 cdb.05
-rw-------. 1 citadel root          8192 17. Feb 10:34 cdb.06
-rw-------. 1 citadel root          8192 19. Apr 2013  cdb.07
-rw-------. 1 citadel root    3220156416  6. Mär 20:48 cdb.08
-rw-------. 1 citadel root      59904000  6. Mär 18:12 cdb.09
-rw-------. 1 citadel root        110592  6. Mär 18:12 cdb.0a
-rw-------. 1 citadel root          8192  6. Mär 16:43 cdb.0b
-rw-------. 1 citadel root          8192 19. Apr 2013  cdb.0c
-rw-------. 1 citadel root          3256  7. Mär 12:18 citadel.config
-rw-------. 1 citadel root            56  7. Mär 12:18 citadel.control
-rw-------. 1 citadel root      10485760  7. Mär 12:18 log.0000001276
-rw-------. 1 citadel citadel     318688  7. Mär 11:54 refcount_adjustments.dat

Thanks in advance for any help on this!

 



[#] Sun Mar 08 2015 07:36:43 EDT from dworz @ Uncensored

Subject: Re: citserver core dump in libev

[Reply] [ReplyQuoted] [Headers] [Print]

Hi

I don't know if this patch is correct, but at least my server is back up and running:

index 94592a1..7d2391c 100644
--- a/modules/c-ares-dns/serv_c-ares-dns.c
+++ b/modules/c-ares-dns/serv_c-ares-dns.c
@@ -586,8 +586,7 @@ void SockStateCb(void *data, int sock, int read, int write)
        IO->Now = ev_now(event_base);
 
        if (read) {
-               if ((IO->DNS.recv_event.fd != sock) &&
-                   (IO->DNS.recv_event.fd != 0)) {
+               if (IO->DNS.recv_event.fd != 0) {
                        EV_DNS_LOG_STOP(DNS.recv_event);
                        ev_io_stop(event_base, &IO->DNS.recv_event);
                }
@@ -602,8 +601,7 @@ void SockStateCb(void *data, int sock, int read, int write)
                ev_io_start(event_base, &IO->DNS.recv_event);
        }
        if (write) {
-               if ((IO->DNS.send_event.fd != sock) &&
-                   (IO->DNS.send_event.fd != 0)) {
+               if (IO->DNS.send_event.fd != 0) {
                        EV_DNS_LOG_STOP(DNS.send_event);
                        ev_io_stop(event_base, &IO->DNS.send_event);
                }

 

I assume the socket gets reused, but sometimes it is randomly the same number as before and then it doesn't get stopped.

What do you think? If it is correct, could you please include it in future version?

bye
 dworz



Go to page: First ... 36 37 38 39 [40] 41 42 43 44 ... Last