UpStare 0.9.12 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News UpStare 0.9.12 (Default branch)
# 1  
Old 09-17-2008
UpStare 0.9.12 (Default branch)

UpStare is a dynamic software updating system for multi-threaded userspace applications that applies immediate updates using stack reconstruction. The program state and the program code are updated immediately in a single step. It is not necessary to wait indefinitely for a quiescent program state. A running algorithm can be updated midstream its execution and resumed from a different point (not necessarily the beginning) of another algorithm. License: Freely Distributable Changes:
This release fixes a critical issue in the runtime in determining which children have died and should be ignored when coordinating an update with children. It also handles non-blocking file descriptors created with open() and pipe(), and calls to select() with a pointer (possibly set to NULL) timeout argument that would block indefinitely. With these changes, the system can update PostgreSQL while multiple clients are connected to it. Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
uname_eoverflow(5)						File Formats Manual						uname_eoverflow(5)

NAME
uname_eoverflow - causes uname() system function to return [EOVERFLOW] if values do not fit in fields VALUES
Failsafe Default Allowed Values DESCRIPTION
The tunable controls whether programs calling the non-expanded version of will be alerted to the fact that the values did not fit in their corresponding fields. When this tunable value is 0, the non-expanded version of will be silent about any truncation of returned values. When this tunable value is 1, the caller will be alerted to the truncation with a non-zero return value and set to Changing this tunable does not affect the current system values returned by In a future version of HP-UX, the function will return no data when (or other errors) are reported. See the uname(2) manpage for informa- tion on Who Is Expected to Change This Tunable? The system administrator may change this tunable when it is necessary to change program behavior in respect to errors. Restrictions on Changing This tunable is dynamic. Changes are effective for all subsequent calls to the non-expanded version of When Should the Value of This Tunable Be Raised? This tunable may be raised to 1 when applications need to be alerted to the error from What are the Side Effects of Raising the Value? Raising the tunable value to 1 causes the non-expanded version of the system function to return a non-zero status and the error if any value cannot fit in its corresponding field of the non-expanded structure. When Should the Value of This Tunable Be Lowered? This tunable should be lowered to 0 when it is necessary to allow applications to proceed with truncated values. This may be the case where the application aborts due to the error but will tolerate the truncated values; for example, because the values are not important to its operation. What are the Side Effects of Lowering the Value? Lowering the tunable value to 0 causes the non-expanded version of the system function silently truncate any values which do not fit in the non-expanded fields. It will not alert the caller with an error when such truncation occurs. What Other Tunable Values Should Be Changed at the Same Time? None. WARNINGS
Setting this tunable to 0 (off) means that applications will not be alerted to truncated values returned by the non-expanded system call. Applications using such truncated values may fail in a non-deterministic manner. As of the HP-UX 11i Version 3 initial release, only the node name value returned by may be truncated as no other fields returned by that function can take on values which exceed the non-expanded field sizes. However, later updates and releases may expand other values, and their corresponding non-expanded fields may also be truncated (or cause the error to be reported. Such expansions will be optional at the discretion of the system administrator. However, upgrading programs to use the expanded version of the system function will avoid future issues. For more information on usage see the whitepaper entitled All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of HP-UX. Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation, some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun- able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was factory installed on your system, see at AUTHOR
was developed by HP. SEE ALSO
uname(2), expanded_node_host_names(5). whitepaper, available on Tunable Kernel Parameters uname_eoverflow(5)