# Any reason why the SCTP\_SENDER\_DRY\_EVENT sctp socket event is not supported by gen\_sctp on Linux?

**URL:** <https://erlangforums.com/t/any-reason-why-the-sctp-sender-dry-event-sctp-socket-event-is-not-supported-by-gen-sctp-on-linux/3150>\
**Category:** Questions / Help\
**Tags:** gen\_sctp, sctp\
**Created:** [December 26, 2023, 6:15pm UTC](https://erlangforums.com/t/any-reason-why-the-sctp-sender-dry-event-sctp-socket-event-is-not-supported-by-gen-sctp-on-linux/3150 "2023-12-26T18:15:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![cristconst](https://erlangforums.com/letter_avatar_proxy/v4/letter/c/ed8c4c/32.png) [@cristconst](https://erlangforums.com/u/cristconst)\
**Post date:** [December 26, 2023, 6:15pm UTC](https://erlangforums.com/t/any-reason-why-the-sctp-sender-dry-event-sctp-socket-event-is-not-supported-by-gen-sctp-on-linux/3150/1 "2023-12-26T18:15:15Z")

</div>

Hi,

Any particular reason why the SCTP\_SENDER\_DRY\_EVENT sctp socket event (notification) is not supported by gen\_sctp on Linux?

Linux supports this event notification. See for example “/usr/include/linux/sctp.h” on a recent Linux distribution:

```erlang
/*
 * 6.1.9. SCTP_SENDER_DRY_EVENT
 *
 * When the SCTP stack has no more user data to send or retransmit, this
 * notification is given to the user. Also, at the time when a user app
 * subscribes to this event, if there is no data to be sent or
 * retransmit, the stack will immediately send up this notification.
 */
struct sctp_sender_dry_event {
        __u16 sender_dry_type;
        __u16 sender_dry_flags;
        __u32 sender_dry_length;
        sctp_assoc_t sender_dry_assoc_id;
};

```

Thanks a lot,  
Cristian

---

<div class="post-metadata">

**Author:** ![jimdigriz](https://erlangforums.com/user_avatar/erlangforums.com/jimdigriz/32/1885_2.png) [@jimdigriz](https://erlangforums.com/u/jimdigriz)\
**Post date:** [December 26, 2023, 9:21pm UTC](https://erlangforums.com/t/any-reason-why-the-sctp-sender-dry-event-sctp-socket-event-is-not-supported-by-gen-sctp-on-linux/3150/2 "2023-12-26T21:21:16Z")

</div>

[Probably due to Erlang not running exclusively on Linux](https://www.erlang.org/doc/man/gen_sctp.html#description).

I have found the OTP team are receptive to GitHub Issues and PR’s so my suggestion is to put together a dirty implementation that resolves your problem, get feedback and then iterate on it to get it into shape for inclusion.

Besides, even if you do not want to contribute, you can just run your own fork of OTP, many do for their deployments.