Xt timer call, XtAppAddTimeout, hangs on system clock jump backwards Post: 303020518

10 More Discussions You Might Find Interesting

1. AIX

AIX 5.3 12 Hour System Clock

Hello Everyone, I have a Domino application running on AIX 5.3 that does time conversions worldwide. It uses the operating system time as a reference for the conversion. My problem is that I need the AIX OS clock to be a 12 hour clock (AM/PM) rather than a 24 hour clock. I have tried the date...

2. UNIX for Dummies Questions & Answers

clock() call returning zero always

Hi, Is there a chance that the clock() call returns 0 eternally??? Using BSD. My RTOS application freezes inconsistently only on particular hosts. When debugging it, I came to see that the RTOS timer does not tick at times. The underlying system call is clock() & it always returns zero when the...

3. UNIX for Advanced & Expert Users

how to differentiate system call from library call

Hi, Ho do I differentiate system call from library call? for example if I am using chmod , how do I find out if it is a system call or library call? Thanks Muru

4. Programming

ABOUT RECV() SYSTEM CALL (regarding timer)

Hi all, I am facing a problem in recv() system call i.e.. in my project i have to implement timer for sending (data) and resending purpose when there is no acknowledgement. is there any way that recv() sys call has its own timer i.e., for ex: recv() has to wait for 10 secs. if any...

5. Programming

Recv() call with timer(time out )

6. Shell Programming and Scripting

Sync Solaris System Clock With PDC Using Cron

Hi, I currently use the ntpdate and date command to sync the internal clock source of my Solaris systems to the primary domain controller. admin@myserver # ntpdate -d -u 192.168.???.??? 14 Jan 17:42:02 ntpdate: ntpdate 3-5.93e+sun 03/06/05 23:16:45 (1.4) transmit(192.168.???.???)...

7. Solaris

System hangs

Hi, today when i started the OS Sun Solaris 10 it hangs on initialization. Following was shown in the end of the screen Initializing system Please wait.... * Please help?

8. Solaris

System hangs (freezes) on system bell/beep

I am running OpenIndiana development version oi_148 32-bit on a seven-year-old Dell Inspiron 8600. Seems to be running fine except for one particular annoyance: It freezes whenever a system bell/beep plays. I have mitigated this by turning the system bell off in gnome-terminal, which I use...

9. SCO

System Clock running at half speed

SCO Openserver 6.0.0 had an issue with a NIC losing it's config on reboot. Netconfig would not allow "view protocol" and apparently zeroed out the existing IP info. Repaired from console. After this event, however, the system clock seems to lose 30 seconds for every RTC minute that passes. As a...

10. UNIX for Advanced & Expert Users

The UNIX clock/timer interrupt

The book The Design of the Unix Operating System speaks of a clock or timer that is used in scheduling. The clock generates interrupts that update priority information for processes and preempt processes in a round-robin fashion. It's apparent that this "clock" is not the same thing as the CPU...

LEARN ABOUT CENTOS

rstream

RSTREAM(1)							     librdmacm								RSTREAM(1)

NAME

       rstream - streaming over RDMA ping-pong test.

SYNOPSIS

       rstream [-s server_address] [-b bind_address] [-B buffer_size]
		      [-I iterations] [-C transfer_count]
		      [-S transfer_size] [-p server_port] [-T test_option]

DESCRIPTION

       Uses the streaming over RDMA protocol (rsocket) to connect and exchange data between a client and server application.

OPTIONS

       -s server_address
	      The  network  name  or  IP address of the server system listening for connections.  The used name or address must route over an RDMA
	      device.  This option must be specified by the client.

       -b bind_address
	      The local network address to bind to.

       -B buffer_size
	      Indicates the size of the send and receive network buffers.

       -I iterations
	      The number of times that the specified number of messages will be exchanged between the client and server.  (default 1000)

       -C transfer_count
	      The number of messages to transfer from the client to the server and back again on each iteration.  (default 1)

       -S transfer_size
	      The size of each send transfer, in bytes.  (default 1000)  If 'all' is specified, rstream will run a  series  of	tests  of  various
	      sizes.

       -p server_port
	      The server's port number.

       -T test_option
	      Specifies test parameters.  Available options are:

       s | socket  - uses standard socket calls to transfer data

       a | async - uses asynchronous operation (e.g. select / poll)

       b | blocking - uses blocking calls

       f | fork - fork server processing (forces -T s option)

       n | nonblocking - uses non-blocking calls

       v | verify - verifies data transfers

NOTES

       Basic  usage  is  to  start rstream on a server system, then run rstream -s server_name on a client system.  By default, rstream will run a
       series of latency and bandwidth performance tests.  Specifying a different iterations, transfer_count, or transfer_size	will  run  a  user
       customized test using default values where none have been specified.

       Because	this  test maps RDMA resources to userspace, users must ensure that they have available system resources and permissions.  See the
       libibverbs README file for additional details.

SEE ALSO

       rdma_cm(7)

librdmacm							    2011-11-16								RSTREAM(1)