9 More Discussions You Might Find Interesting
1. UNIX and Linux Applications
HI All-
We have script like the followinga='h1 '
b='12434 '
c=' fagkasdbkZ<M'
output=$a$b$c
echo $output > /home/dsomasun/fil_concat.txtBut in the output file spaces are truncated and Output is coming like the belowh1 1234 fagkasdbkZ<M
please advise
Please wrap all code,... (4 Replies)
Discussion started by: dhilipans1988
4 Replies
2. UNIX for Advanced & Expert Users
Operating System: Solaris 10, Shell
We are outputting the results of our scripts to the stderr file. However we have encountered a problem where some of the lines in the file are truncated.
Is there a way to increase the terminal or column size within the script so that this does not... (4 Replies)
Discussion started by: fazzasx
4 Replies
3. Filesystems, Disks and Memory
Sir, my apologies for I had put this question in a different forum earlier.
I am running an appliction in SCO 5.6. If the records are more than one lakh, the output file is getting truncated to one lakh. Please help me in rectifying the issue whereby it allows creation of output with more than... (0 Replies)
Discussion started by: chssastry
0 Replies
4. UNIX for Advanced & Expert Users
I searched and could not find an answer to this, and am having difficulty, so I would appreciate any assistance that can be offered.
We're experiencing logs that are having all characters after the 850th one written being truncated. I am wondering if there is a default limit to the syslog... (1 Reply)
Discussion started by: Puck
1 Replies
5. UNIX for Advanced & Expert Users
Operating system - Solaris 8, Korn shell, xterm
Command
/usr/proc/bin/ptree
outputs the process tree exactly as I want with all detail
However,
/usr/proc/bin/ptree | more
truncates the process descriptions at an 80 character point. If the process tree has marched enough to the right,... (3 Replies)
Discussion started by: JerryHone
3 Replies
6. AIX
folks;
i need help with a truncation problem in AIX when running "ps" command. when i run ps in SUN, i got the full output but when i run it in AIX the output is truncated. is there any arguments i can pass to give longer output so i can overcome the issue?
here's the details:(please note the... (2 Replies)
Discussion started by: moe2266
2 Replies
7. UNIX for Advanced & Expert Users
Hi,
I have a program that gets called from the front end of my application. Actually it creates some temporary files and uses them and deletes them at last. But sometimes, say once in 6 times, some of these temporary files are getting truncated in the middle and because of this my program is... (9 Replies)
Discussion started by: venkatmyname
9 Replies
8. UNIX for Advanced & Expert Users
Hi,
I'm using the vi that comes with Solaris 2.8. When vi a file with lines that have long continuous characters e.g. more than 256 chars, these lines got truncated. This is a known limitation of the out of the box Solaris vi, and there is a suggestion to get another vi. Is there an... (0 Replies)
Discussion started by: selur-xinu
0 Replies
9. Solaris
we aheva couple of old sun OS boxes, that we are trying to parse /usr/ucb/ps output.
However it seems that something is occuring that is causeing th output of "/usr/ucb/ps -auxwww" to cut short the process name, whereas "ps -eaf" can display the entire process name.
It will work for a while... (2 Replies)
Discussion started by: adralph
2 Replies
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)