sr-dev November 2016

sr-dev@lists.kamailio.org

27 participants
289 discussions

[kamailio/kamailio] tm: only call onsend_route when there is an original incoming request (#861)

by Timmo Verlaan

- fix for dispatcher ping, see GH #859 - regression introduced by 2f080bd You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/861 -- Commit Summary -- * tm: only call onsend_route when there is an original incoming request -- File Changes -- M modules/tm/uac.c (2) -- Patch Links -- https://github.com/kamailio/kamailio/pull/861.patch https://github.com/kamailio/kamailio/pull/861.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/861

7 years, 10 months

git:master:9a1547e8: core: check required parameters for execution of onsend_route

by Daniel-Constantin Mierla

Module: kamailio Branch: master Commit: 9a1547e8815e697351b0795bb3b4e308e5440a6d URL: https://github.com/kamailio/kamailio/commit/9a1547e8815e697351b0795bb3b4e30… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2016-11-16T16:32:14+01:00 core: check required parameters for execution of onsend_route - alternative to GH #861 --- Modified: onsend.h --- Diff: https://github.com/kamailio/kamailio/commit/9a1547e8815e697351b0795bb3b4e30… Patch: https://github.com/kamailio/kamailio/commit/9a1547e8815e697351b0795bb3b4e30… --- diff --git a/onsend.h b/onsend.h index cba56f4..8360ff2 100644 --- a/onsend.h +++ b/onsend.h @@ -65,6 +65,10 @@ static inline int run_onsend(struct sip_msg* orig_msg, struct dest_info* dst, snd_flags_t rpl_snd_flags_bak; sr_kemi_eng_t *keng = NULL; + if(orig_msg==NULL || dst==NULL || buf==NULL) { + LM_DBG("required parameters are not available - ignoring\n"); + return 1; + } ret=1; if (onsend_rt.rlist[DEFAULT_RT]){ onsnd_info.to=&dst->to;

7 years, 10 months

git:master:092ee821: ims_registrar_scscf: Properly handle the case, when no user-data-xml was provided during SAR (due to the already existing user-data-xml from previous SAR)

by Carsten Bock

Module: kamailio Branch: master Commit: 092ee821752d39eae5155c9b469e6e6d8e2fe9fe URL: https://github.com/kamailio/kamailio/commit/092ee821752d39eae5155c9b469e6e6… Author: Carsten Bock <carsten(a)ng-voice.com> Committer: Carsten Bock <carsten(a)ng-voice.com> Date: 2016-11-15T16:40:56+01:00 ims_registrar_scscf: Properly handle the case, when no user-data-xml was provided during SAR (due to the already existing user-data-xml from previous SAR) --- Modified: modules/ims_registrar_scscf/cxdx_sar.c Modified: modules/ims_registrar_scscf/save.c --- Diff: https://github.com/kamailio/kamailio/commit/092ee821752d39eae5155c9b469e6e6… Patch: https://github.com/kamailio/kamailio/commit/092ee821752d39eae5155c9b469e6e6… --- diff --git a/modules/ims_registrar_scscf/cxdx_sar.c b/modules/ims_registrar_scscf/cxdx_sar.c index 876160f..877c657 100644 --- a/modules/ims_registrar_scscf/cxdx_sar.c +++ b/modules/ims_registrar_scscf/cxdx_sar.c @@ -250,24 +250,11 @@ void async_cdp_callback(int is_timeout, void *param, AAAMessage *saa, long elaps } } - if (data->sar_assignment_type == AVP_IMS_SAR_REGISTRATION || data->sar_assignment_type == AVP_IMS_SAR_RE_REGISTRATION) { - if (s) { - if (build_p_associated_uri(s) != 0) { - LM_ERR("Unable to build p_associated_uri\n"); - rerrno = R_SAR_FAILED; - goto error; - } - } - - } - - if (s) { - //here we update the contacts and also build the new contact header for the 200 OK reply - if (update_contacts(req, data->domain, &data->public_identity, data->sar_assignment_type, &s, &ccf1, &ccf2, &ecf1, &ecf2, &data->contact_header) <= 0) { - LM_ERR("Error processing REGISTER\n"); - rerrno = R_SAR_FAILED; - goto error; - } + //here we update the contacts and also build the new contact header for the 200 OK reply + if (update_contacts(req, data->domain, &data->public_identity, data->sar_assignment_type, &s, &ccf1, &ccf2, &ecf1, &ecf2, &data->contact_header) <= 0) { + LM_ERR("Error processing REGISTER\n"); + rerrno = R_SAR_FAILED; + goto error; } if (data->contact_header) { diff --git a/modules/ims_registrar_scscf/save.c b/modules/ims_registrar_scscf/save.c index 2969ef9..962a65f 100644 --- a/modules/ims_registrar_scscf/save.c +++ b/modules/ims_registrar_scscf/save.c @@ -832,6 +832,7 @@ int update_contacts(struct sip_msg* msg, udomain_t* _d, } //now build the contact buffer to be include in the reply message and unlock build_contact(impu_rec, contact_header); + build_p_associated_uri(*s); notify_subscribers(impu_rec, 0, 0); ul.unlock_udomain(_d, public_identity); break; @@ -855,6 +856,7 @@ int update_contacts(struct sip_msg* msg, udomain_t* _d, } //build the contact buffer for all registered contacts on explicit IMPU build_contact(impu_rec, contact_header); + build_p_associated_uri(impu_rec->s); subscription = impu_rec->s; if (!subscription) { @@ -878,7 +880,7 @@ int update_contacts(struct sip_msg* msg, udomain_t* _d, //now update the implicit set for (i = 0; i < subscription->service_profiles_cnt; i++) { for (j = 0; j < subscription->service_profiles[i].public_identities_cnt; j++) { - pi = &((*s)->service_profiles[i].public_identities[j]); + pi = &(subscription->service_profiles[i].public_identities[j]); if (memcmp(public_identity->s, pi->public_identity.s, public_identity->len) == 0) { //we don't need to update the explicit IMPU LM_DBG("Ignoring explicit identity <%.*s>, updating later.....\n", public_identity->len, public_identity->s);

7 years, 10 months

git:master:13b4cc67: modules: readme files regenerated - auth_identity ...

by Kamailio Dev

Module: kamailio Branch: master Commit: 13b4cc672aa20ae0b8ec4aafdc7c4ab56f593149 URL: https://github.com/kamailio/kamailio/commit/13b4cc672aa20ae0b8ec4aafdc7c4ab… Author: Kamailio Dev <kamailio.dev(a)kamailio.org> Committer: Kamailio Dev <kamailio.dev(a)kamailio.org> Date: 2016-11-15T14:46:26+01:00 modules: readme files regenerated - auth_identity ... --- Modified: modules/auth_identity/README Modified: modules/xcap_client/README --- Diff: https://github.com/kamailio/kamailio/commit/13b4cc672aa20ae0b8ec4aafdc7c4ab… Patch: https://github.com/kamailio/kamailio/commit/13b4cc672aa20ae0b8ec4aafdc7c4ab… --- diff --git a/modules/auth_identity/README b/modules/auth_identity/README index d9761bd..5ffdd5d 100644 --- a/modules/auth_identity/README +++ b/modules/auth_identity/README @@ -59,6 +59,7 @@ Gergely Kovacs 7. Authorizer service examples 8. Verifier service examples + 9. Remarks List of Examples @@ -124,6 +125,7 @@ Chapter 1. Admin Guide 7. Authorizer service examples 8. Verifier service examples + 9. Remarks 1. Overview @@ -535,3 +537,12 @@ route[VERIFY] } } ... + +9. Remarks + + Note: libcurl leak in CentOS 6 - this module uses libcurl library and + in case if you are using CentOS 6, be aware that standard + libcurl-7.19.7-52 has a memory leak. To fix this memory, install + libcurl from city-fan repository. More details at: + https://www.digitalocean.com/community/questions/how-to-upgrade-curl-in + -centos6 diff --git a/modules/xcap_client/README b/modules/xcap_client/README index 3606046..0f7875f 100644 --- a/modules/xcap_client/README +++ b/modules/xcap_client/README @@ -33,6 +33,8 @@ Anca-Maria Vamanu 5.1. refreshXcapDoc + 6. Remarks + 2. Developer Guide 1. bind_xcap_api(xcap_api_t* api) @@ -69,6 +71,8 @@ Chapter 1. Admin Guide 5.1. refreshXcapDoc + 6. Remarks + 1. Overview The modules is a XCAP client for Kamailio that can be used by other @@ -194,6 +198,15 @@ modparam("xcap_client", "query_period", 50) _empty_line_ ... +6. Remarks + + Note: libcurl leak in CentOS 6 - this module uses libcurl library and + in case if you are using CentOS 6, be aware that standard + libcurl-7.19.7-52 has a memory leak. To fix this memory, install + libcurl from city-fan repository. More details at: + https://www.digitalocean.com/community/questions/how-to-upgrade-curl-in + -centos6 + Chapter 2. Developer Guide Table of Contents

7 years, 10 months

[kamailio/kamailio] Updated documentation of modules which are impacted by memory leak in… (#853)

by Jurijs Ivolga

Updated documentation for modules who uses libcurl, regarding memory leak in Centos 6 libcurl library. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/853 -- Commit Summary -- * Updated documentation of modules which are impacted by memory leak in Centos 6 standard libcurl library. -- File Changes -- M modules/auth_identity/doc/auth_identity.xml (6) M modules/http_async_client/doc/http_async_client_admin.xml (6) M modules/http_client/doc/http_client_admin.xml (6) M modules/utils/doc/utils_admin.xml (6) M modules/xcap_client/doc/xcap_client_admin.xml (6) -- Patch Links -- https://github.com/kamailio/kamailio/pull/853.patch https://github.com/kamailio/kamailio/pull/853.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/853

7 years, 10 months

git:master:bff8cbb0: auth_identity: added remarks section with note about libcurl leak on centos 6

by Daniel-Constantin Mierla

Module: kamailio Branch: master Commit: bff8cbb0a03deaea7b9c32f6c6d74525c34be5dd URL: https://github.com/kamailio/kamailio/commit/bff8cbb0a03deaea7b9c32f6c6d7452… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2016-11-15T14:40:56+01:00 auth_identity: added remarks section with note about libcurl leak on centos 6 - based on GH #853 --- Modified: modules/auth_identity/doc/auth_identity.xml --- Diff: https://github.com/kamailio/kamailio/commit/bff8cbb0a03deaea7b9c32f6c6d7452… Patch: https://github.com/kamailio/kamailio/commit/bff8cbb0a03deaea7b9c32f6c6d7452… --- diff --git a/modules/auth_identity/doc/auth_identity.xml b/modules/auth_identity/doc/auth_identity.xml index a3242ca..e049e5d 100644 --- a/modules/auth_identity/doc/auth_identity.xml +++ b/modules/auth_identity/doc/auth_identity.xml @@ -225,5 +225,16 @@ route[VERIFY] ... ]]></programlisting> </section> + <section id="auth_identity.s.remarks"> + <title>Remarks</title> + <para> + Note: libcurl leak in CentOS 6 - this module uses libcurl library + and in case if you are using CentOS 6, be aware that standard + libcurl-7.19.7-52 has a memory leak. To fix this memory, install + libcurl from city-fan repository. More details at: + <ulink url="https://www.digitalocean.com/community/questions/how-to-upgrade-curl-in-cen…"> + https://www.digitalocean.com/community/questions/how-to-upgrade-curl-in-cen…</ulink> + </para> + </section> </chapter> </book>

7 years, 10 months

git:master:c1e621d5: xcap_client: added remarks section with note about libcurl leak on centos 6

by Daniel-Constantin Mierla

Module: kamailio Branch: master Commit: c1e621d5347b32e04588efb93204ccdf13c3a2e6 URL: https://github.com/kamailio/kamailio/commit/c1e621d5347b32e04588efb93204ccd… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2016-11-15T14:40:25+01:00 xcap_client: added remarks section with note about libcurl leak on centos 6 - based on GH #853 --- Modified: modules/xcap_client/doc/xcap_client_admin.xml --- Diff: https://github.com/kamailio/kamailio/commit/c1e621d5347b32e04588efb93204ccd… Patch: https://github.com/kamailio/kamailio/commit/c1e621d5347b32e04588efb93204ccd… --- diff --git a/modules/xcap_client/doc/xcap_client_admin.xml b/modules/xcap_client/doc/xcap_client_admin.xml index f33f2dc..9e98f0e 100644 --- a/modules/xcap_client/doc/xcap_client_admin.xml +++ b/modules/xcap_client/doc/xcap_client_admin.xml @@ -205,6 +205,17 @@ _empty_line_ </section> </section> + <section id="xcap_client.s.remarks"> + <title>Remarks</title> + <para> + Note: libcurl leak in CentOS 6 - this module uses libcurl library + and in case if you are using CentOS 6, be aware that standard + libcurl-7.19.7-52 has a memory leak. To fix this memory, install + libcurl from city-fan repository. More details at: + <ulink url="https://www.digitalocean.com/community/questions/how-to-upgrade-curl-in-cen…"> + https://www.digitalocean.com/community/questions/how-to-upgrade-curl-in-cen…</ulink> + </para> + </section> </chapter>

7 years, 10 months

git:master:01a9e1b1: htable: support to execute kemi callbacks on event route for item expiration

by Daniel-Constantin Mierla

Module: kamailio Branch: master Commit: 01a9e1b1935e7eddd7ccd5794a9669e75e201f2b URL: https://github.com/kamailio/kamailio/commit/01a9e1b1935e7eddd7ccd5794a9669e… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2016-11-14T17:01:48+01:00 htable: support to execute kemi callbacks on event route for item expiration --- Modified: modules/htable/ht_api.c Modified: modules/htable/ht_api.h --- Diff: https://github.com/kamailio/kamailio/commit/01a9e1b1935e7eddd7ccd5794a9669e… Patch: https://github.com/kamailio/kamailio/commit/01a9e1b1935e7eddd7ccd5794a9669e…

7 years, 10 months

Re: [sr-dev] [SR-Users] [CFP] FOSDEM 2017, RTC devroom, speakers, volunteers neeeded

by Daniel-Constantin Mierla

Hello, a short reminder for those interested in submitting a talk proposal for FOSDEM 2017 -- see the details in the initial email. Cheers, Daniel On 24/10/16 11:09, FOSDEM RTC Team wrote: > FOSDEM is one of the world's premier meetings of free software developers, > with over five thousand people attending each year. FOSDEM 2017 > takes place 4-5 February 2017 in Brussels, Belgium. https://fosdem.org > > This email contains information about: > - Real-Time communications dev-room and lounge, > - speaking opportunities, > - volunteering in the dev-room and lounge, > - related events around FOSDEM, including the XMPP summit, > - social events (the legendary FOSDEM Beer Night and Saturday night dinners > provide endless networking opportunities), > - the Planet aggregation sites for RTC blogs > > Call for participation - Real Time Communications (RTC) > ======================================================= > > The Real-Time dev-room and Real-Time lounge is about all things involving > real-time communication, including: XMPP, SIP, WebRTC, telephony, > mobile VoIP, codecs, peer-to-peer, privacy and encryption. The dev-room > is a successor to the previous XMPP and telephony dev-rooms. > We are looking for speakers for the dev-room and volunteers and > participants for the tables in the Real-Time lounge. > > The dev-room is only on Saturday, 4 February 2017. The lounge will > be present for both days. > > To discuss the dev-room and lounge, please join the FSFE-sponsored > Free RTC mailing list: https://lists.fsfe.org/mailman/listinfo/free-rtc > > To be kept aware of major developments in Free RTC, without being on the > discussion list, please join the Free-RTC Announce list: > http://lists.freertc.org/mailman/listinfo/announce > > Speaking opportunities > ---------------------- > > Note: if you used FOSDEM Pentabarf before, please use the same account/username > > Real-Time Communications dev-room: deadline 23:59 UTC on 17 November. > Please use the Pentabarf system to submit a talk proposal for the > dev-room. On the "General" tab, please look for the "Track" option and > choose "Real-Time devroom". https://penta.fosdem.org/submission/FOSDEM17/ > > Other dev-rooms and lightning talks: some speakers may find their topic is > in the scope of more than one dev-room. It is encouraged to apply to more > than one dev-room and also consider proposing a lightning talk, but please > be kind enough to tell us if you do this by filling out the notes in the form. > You can find the full list of dev-rooms at > https://www.fosdem.org/2017/schedule/tracks/ > and apply for a lightning talk at https://fosdem.org/submit > > Main track: the deadline for main track presentations is 23:59 UTC > 31 October. Leading developers in the Real-Time Communications > field are encouraged to consider submitting a presentation to > the main track at https://fosdem.org/submit > > First-time speaking? > -------------------- > > FOSDEM dev-rooms are a welcoming environment for people who have never > given a talk before. Please feel free to contact the dev-room administrators > personally if you would like to ask any questions about it. > > Submission guidelines > --------------------- > > The Pentabarf system will ask for many of the essential details. Please > remember to re-use your account from previous years if you have one. > > In the "Submission notes", please tell us about: > - the purpose of your talk > - any other talk applications (dev-rooms, lightning talks, main track) > - availability constraints and special needs > > You can use HTML and links in your bio, abstract and description. > > If you maintain a blog, please consider providing us with the > URL of a feed with posts tagged for your RTC-related work. > > We will be looking for relevance to the conference and dev-room themes, > presentations aimed at developers of free and open source software about > RTC-related topics. > > Please feel free to suggest a duration between 20 minutes and 55 minutes > but note that the final decision on talk durations will be made by the > dev-room administrators. As the two previous dev-rooms have been > combined into one, we may decide to give shorter slots than in previous > years so that more speakers can participate. > > Please note FOSDEM aims to record and live-stream all talks. > The CC-BY license is used. > > Volunteers needed > ================= > > To make the dev-room and lounge run successfully, we are looking for > volunteers: > > - FOSDEM provides video recording equipment and live streaming, > volunteers are needed to assist in this > - organizing one or more restaurant bookings (dependending upon number of > participants) for the evening of Saturday, 4 February > - participation in the Real-Time lounge > - helping attract sponsorship funds for the dev-room to pay for the > Saturday night dinner and any other expenses > - circulating this Call for Participation to other mailing lists > > See the mailing list discussion for more details about volunteering: > https://lists.fsfe.org/pipermail/free-rtc/2016-October/000285.html > > Related events - XMPP and RTC summits > ===================================== > > The XMPP Standards Foundation (XSF) has traditionally held a summit > in the days before FOSDEM. There is discussion about a similar > summit taking place on 2 and 3 February 2017 > http://wiki.xmpp.org/web/Summit_21 - please join the mailing > list for details: http://mail.jabber.org/mailman/listinfo/summit > > We are also considering a more general RTC or telephony summit, > potentially in collaboration with the XMPP summit. > Please join the Free-RTC mailing list and send an email if you would > be interested in participating, sponsoring or hosting such an event. > > Social events and dinners > ========================= > > The traditional FOSDEM beer night occurs on Friday, 3 February. > > On Saturday night, there are usually dinners associated with > each of the dev-rooms. Most restaurants in Brussels are not so > large so these dinners have space constraints and reservations are > essential. Please subscribe to the Free-RTC mailing list for > further details about the Saturday night dinner options and how > you can register for a seat: https://lists.fsfe.org/mailman/listinfo/free-rtc > > Spread the word and discuss > =========================== > > If you know of any mailing lists where this CfP would be relevant, please > forward this email. If this dev-room excites you, please blog or microblog > about it, especially if you are submitting a talk. > > If you regularly blog about RTC topics, please send details about your > blog to the planet site administrators: > > All projects http://planet.freertc.org planet(a)freertc.org > > XMPP http://planet.jabber.org ralphm(a)ik.nu > > SIP http://planet.sip5060.net planet(a)sip5060.net > (Español) http://planet.sip5060.net/es/ planet(a)sip5060.net > > Please also link to the Planet sites from your own blog or web site as > this helps everybody in the free real-time communications community. > > Contact > ======= > > For any private queries, contact us directly using the address > fosdem-rtc-admin(a)freertc.org and for any other queries please ask on > the Free-RTC mailing list: > https://lists.fsfe.org/mailman/listinfo/free-rtc > > The dev-room administration team: > > Saúl Ibarra Corretgé <saghul(a)gmail.com> > Iain R. Learmonth <irl(a)debian.org> > Ralph Meijer <ralphm(a)ik.nu> > Daniel-Constantin Mierla <miconda(a)gmail.com> > Daniel Pocock <daniel(a)pocock.pro> > > > > _______________________________________________ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > sr-users(a)lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Training, Berlin, Nov 28-30, 2016 - http://www.asipto.com

7 years, 10 months

git:master:39b16212: htable: use lookup instead of get for event route item expiration

by Daniel-Constantin Mierla

Module: kamailio Branch: master Commit: 39b162122964bc9ef04b0fa32b9ce9eaf1d9530b URL: https://github.com/kamailio/kamailio/commit/39b162122964bc9ef04b0fa32b9ce9e… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2016-11-14T16:30:07+01:00 htable: use lookup instead of get for event route item expiration - get creates an empty structure which is not used --- Modified: modules/htable/ht_api.c Modified: modules/htable/ht_api.h --- Diff: https://github.com/kamailio/kamailio/commit/39b162122964bc9ef04b0fa32b9ce9e… Patch: https://github.com/kamailio/kamailio/commit/39b162122964bc9ef04b0fa32b9ce9e… --- diff --git a/modules/htable/ht_api.c b/modules/htable/ht_api.c index b96ff13..64e9058 100644 --- a/modules/htable/ht_api.c +++ b/modules/htable/ht_api.c @@ -362,7 +362,7 @@ int ht_init_tables(void) { strcpy(route_name, "htable:expired:"); strncat(route_name, ht->name.s, ht->name.len); - ht->evrt_expired = route_get(&event_rt, route_name); + ht->evrt_expired = route_lookup(&event_rt, route_name); if (ht->evrt_expired < 0 || event_rt.rlist[ht->evrt_expired] == NULL) @@ -1079,24 +1079,22 @@ void ht_handle_expired_record(ht_t *ht, ht_cell_t *cell) LM_DBG("running event_route[htable:expired:%.*s]\n", ht->name.len, ht->name.s); - ht_expired_run_event_route(ht->evrt_expired); + ht_expired_run_event_route(ht); ht_expired_cell = NULL; } -void ht_expired_run_event_route(int routeid) +void ht_expired_run_event_route(ht_t *ht) { int backup_rt; sip_msg_t *fmsg; - if (routeid < 0 || event_rt.rlist[routeid] == NULL) - { + if (ht->evrt_expired < 0 || event_rt.rlist[ht->evrt_expired] == NULL) { LM_DBG("route does not exist\n"); return; } - if (faked_msg_init() < 0) - { + if (faked_msg_init() < 0) { LM_ERR("faked_msg_init() failed\n"); return; } @@ -1106,7 +1104,7 @@ void ht_expired_run_event_route(int routeid) backup_rt = get_route_type(); set_route_type(EVENT_ROUTE); - run_top_route(event_rt.rlist[routeid], fmsg, 0); + run_top_route(event_rt.rlist[ht->evrt_expired], fmsg, 0); set_route_type(backup_rt); } diff --git a/modules/htable/ht_api.h b/modules/htable/ht_api.h index a37e98f..5169378 100644 --- a/modules/htable/ht_api.h +++ b/modules/htable/ht_api.h @@ -18,7 +18,7 @@ * along with this program; if not, write to the Free Software * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA */ - + #ifndef _HT_API_H_ #define _HT_API_H_ @@ -103,7 +103,7 @@ int ht_db_sync_tables(void); int ht_has_autoexpire(void); void ht_timer(unsigned int ticks, void *param); void ht_handle_expired_record(ht_t *ht, ht_cell_t *cell); -void ht_expired_run_event_route(int routeid); +void ht_expired_run_event_route(ht_t *ht); int ht_set_cell_expire(ht_t *ht, str *name, int type, int_str *val); int ht_get_cell_expire(ht_t *ht, str *name, unsigned int *val);

7 years, 10 months

← Newer
1
...
9
10
11
12
13
14
15
...
29
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev November 2016