search for: run_server

...quot;CLIENTDONE"); >+ >+ close(fd); >+} >+ > static struct test_case test_cases[] = { > { > .name = "SOCK_STREAM connection reset", >@@ -1250,6 +1378,16 @@ static struct test_case test_cases[] = { > .run_client = test_seqpacket_msg_peek_client, > .run_server = test_seqpacket_msg_peek_server, > }, >+ { >+ .name = "SOCK_STREAM SHUT_WR", >+ .run_client = test_stream_shutwr_client, >+ .run_server = test_stream_shutwr_server, >+ }, >+ { >+ .name = "SOCK_STREAM SHUT_RD", >+ .run_client = test_stream_shutrd...

...-25 17:20:14 ERROR: ebtables not usable, disabling ethernet bridge firewall. Nov 25 17:20:14 ns1.currencybooking.com firewalld[2865]: 2015-11-25 17:20:14 FATAL ERROR: No IPv4 and IPv6 firewall. Nov 25 17:20:14 ns1.currencybooking.com firewalld[2865]: 2015-11-25 17:20:14 ERROR: Raising SystemExit in run_server Shiva Prasad Nath 92981134 On Wed, Nov 25, 2015 at 3:07 PM, John R Pierce <pierce at hogranch.com> wrote: > On 11/24/2015 10:18 PM, Siva Prasad Nath wrote: > >> If possible advice me for below error. >> >> [root at ns1 sysconfig]# iptables-restore < /etc/syscon...

The vsock_diag.ko module already has a test suite but the core AF_VSOCK functionality has no tests. This patch series adds several test cases that exercise AF_VSOCK SOCK_STREAM socket semantics (send/recv, connect/accept, half-closed connections, simultaneous connections). The v1 of this series was originally sent by Stefan. v3: - Patch 6: * check the byte received in the recv_byte() * use

...OR: could not insert 'nf_conntrack': Unknown symbol in module, or unknown parameter (see dmesg) modprobe: ERROR: Error running install command for nf_conntrack modprobe: ERROR: could not insert 'nf_conntrack': Operation not permitted 2019-12-11 19:11:25 ERROR: Raising SystemExit in run_server -- Adri P. van Bloois "Elegance is not a dispensable luxury but a factor that decides between success and failure." Edsger W. Dijkstra

...LTICONN_NFDS; i++) + close(fds[i]); +} + +static struct test_case test_cases[] = { + { + .name = "SOCK_STREAM connection reset", + .run_client = test_stream_connection_reset, + }, + { + .name = "SOCK_STREAM client close", + .run_client = test_stream_client_close_client, + .run_server = test_stream_client_close_server, + }, + { + .name = "SOCK_STREAM server close", + .run_client = test_stream_server_close_client, + .run_server = test_stream_server_close_server, + }, + { + .name = "SOCK_STREAM multiple connections", + .run_client = test_stream_multiconn_c...

...6 02:43:16 ERROR: ebtables not usable, disabling ethernet bridge firewall. Nov 26 02:43:16 ns1.currencybooking.com firewalld[35808]: 2015-11-26 02:43:16 FATAL ERROR: No IPv4 and IPv6 firewall. Nov 26 02:43:16 ns1.currencybooking.com firewalld[35808]: 2015-11-26 02:43:16 ERROR: Raising SystemExit in run_server [root at ns1 httpd]# ERROR: ebtables not usable, disabling ethernet bridge firewall.^C [root at ns1 httpd]# firewall-cmd --state not running Shiva Prasad Nath 92981134

...eln("REPLY1"); >+ >+ close(fd); >+} >+ > static struct test_case test_cases[] = { > { > .name = "SOCK_STREAM connection reset", >@@ -1038,6 +1114,11 @@ static struct test_case test_cases[] = { > .run_client = test_seqpacket_inv_buf_client, > .run_server = test_seqpacket_inv_buf_server, > }, >+ { >+ .name = "SOCK_STREAM virtio skb merge", >+ .run_client = test_stream_virtio_skb_merge_client, >+ .run_server = test_stream_virtio_skb_merge_server, >+ }, > {}, > }; > >-- >2.25.1 >

The vsock_diag.ko module already has a test suite but the core AF_VSOCK functionality has no tests. This patch series adds several test cases that exercise AF_VSOCK SOCK_STREAM socket semantics (send/recv, connect/accept, half-closed connections, simultaneous connections). Stefan: Do you think we should have a single application or is better to split it in single tests (e.g.

...me = "SOCK_STREAM connection reset", > + .run_client = test_stream_connection_reset, > + }, > + { > + .name = "SOCK_STREAM client close", > + .run_client = test_stream_client_close_client, > + .run_server = test_stream_client_close_server, > + }, > + { > + .name = "SOCK_STREAM server close", > + .run_client = test_stream_server_close_client, > + .run_server = test_stream_server_close_server, > + }, > + {...

...me = "SOCK_STREAM connection reset", > + .run_client = test_stream_connection_reset, > + }, > + { > + .name = "SOCK_STREAM client close", > + .run_client = test_stream_client_close_client, > + .run_server = test_stream_client_close_server, > + }, > + { > + .name = "SOCK_STREAM server close", > + .run_client = test_stream_server_close_client, > + .run_server = test_stream_server_close_server, > + }, > + {...

...les not usable, > disabling ethernet bridge firewall. Nov 25 17:20:14 > ns1.currencybooking.com firewalld[2865]: 2015-11-25 17:20:14 FATAL > ERROR: No IPv4 and IPv6 firewall. Nov 25 17:20:14 > ns1.currencybooking.com firewalld[2865]: 2015-11-25 17:20:14 ERROR: > Raising SystemExit in run_server Are you sure that you're running CentOS 7 and not some kind of VPS (using a shared kernel, and on which you can't modify iptables rules) ? What about "modinfo ip_tables ; uname -a " ? Cheers, - -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | tw...

Hi, If possible advice me for below error. [root at ns1 sysconfig]# iptables-restore < /etc/sysconfig/iptables iptables-restore: line 2 failed Thanks in advance.

...disabling ethernet bridge firewall. Nov 25 17:20:14 > > ns1.currencybooking.com firewalld[2865]: 2015-11-25 17:20:14 FATAL > > ERROR: No IPv4 and IPv6 firewall. Nov 25 17:20:14 > > ns1.currencybooking.com firewalld[2865]: 2015-11-25 17:20:14 ERROR: > > Raising SystemExit in run_server > > Are you sure that you're running CentOS 7 and not some kind of VPS > (using a shared kernel, and on which you can't modify iptables rules) ? > What about "modinfo ip_tables ; uname -a " ? > > Cheers, > > - -- > Fabian Arrotin > The CentOS Project...

This patch series contains a set of patches making minios rather easier to use, from an application development point of view. Overview of patches: 1 Command line argument parsing support, from Xen. 2 Weak console handler function. 3 Build system tweaks for application directories. 4 Trailing whitespace cleanup. (because it is very messy) Patch 4 is likely to be more controversial than