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. Post Here to Contact Site Administrators and Moderators
Sir, my apologies for not being able to correspond for a long time.
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 one lakh... (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
COMPAT_IBCS2(8) BSD System Manager's Manual COMPAT_IBCS2(8)
NAME
compat_ibcs2 -- setup procedure for running iBCS2 binaries
DESCRIPTION
NetBSD supports running Intel Binary Compatibility Standard 2 (iBCS2) binaries. This only applies to i386 systems for now. Binaries are
supported from SCO UNIX and other systems derived from AT&T System V Release 3 UNIX. iBCS2 support is only well tested using SCO binaries.
XENIX binaries are also supported although not as well tested. SVR4 binaries are supported by the COMPAT_SVR4 option.
iBCS2 supports COFF, ELF, and x.out (XENIX) binary formats. Binaries from SCO OpenServer (version 5.x) are the only ELF binaries that have
been tested. Most programs should work, but not ones that use or depend on:
kernel internal data structures
STREAMS drivers (other than TCP/IP sockets)
local X displays (uses a STREAMS pipe)
virtual 8086 mode
The iBCS2 compatibility feature is active for kernels compiled with the COMPAT_IBCS2 option enabled. If support for iBCS2 ELF executables is
desired, the EXEC_ELF32 option should be enabled in addition to COMPAT_IBCS2.
Many COFF-format programs and most ELF-format programs are dynamically linked. This means that you will also need the shared libraries that
the program depends on. Also, you will need to create a ``shadow root'' directory for iBCS2 binaries on your NetBSD system. This directory
is named /emul/ibcs2. Any file operations done by iBCS2 programs run under NetBSD will look in this directory first. So, if an iBCS2 pro-
gram opens, for example, /etc/passwd, NetBSD will first try to open /emul/ibcs2/etc/passwd, and if that does not exist open the 'real'
/etc/passwd file. It is recommended that you install iBCS2 packages that include configuration files, etc. under /emul/ibcs2, to avoid nam-
ing conflicts with possible NetBSD counterparts. Shared libraries should also be installed in the shadow tree.
Generally, you will need to look for the shared libraries that iBCS2 binaries depend on only the first few times that you install an iBCS2
program on your NetBSD system. After a while, you will have a sufficient set of iBCS2 shared libraries on your system to be able to run
newly imported iBCS2 binaries without any extra work.
Setting up shared libraries
How to get to know which shared libraries iBCS2 binaries need, and where to get them? Depending on the file type of the executable, there are
different possibilities (when following these instructions: you will need to be root on your NetBSD system to do the necessary installation
steps).
COFF binaries You can simply copy all of the available shared libraries since they are fairly small in size. The COFF shared libraries are
typically found in /shlib and can be obtained from the following sources:
SCO UNIX version 3.x (aka ODT)
SCO UNIX version 5.x (aka OpenServer)
SCO UnixWare
Many versions of SVR4.2/x86
After copying the shared libraries, you should have at least the following files on your system:
/emul/ibcs2/shlib/libc_s
/emul/ibcs2/shlib/libnsl_s
/emul/ibcs2/shlib/protlib_s
ELF binaries You can simply copy all of the available shared libraries from the source system or distribution or use ldd(1) to determine
the libraries required by a specific binary.
After copying the shared libraries, you should have at least the following files on your system:
/emul/ibcs2/usr/lib/libc.so.1
/emul/ibcs2/usr/lib/libcrypt.so
/emul/ibcs2/usr/lib/libndbm.so
/emul/ibcs2/usr/lib/libsocket.so.1
If you don't have access to a SCO system, you will need to get the extra files you need from a SCO distribution. As of January 1998, SCO
sells a copy of SCO OpenServer (iBCS2) and/or SCO UnixWare (SVR4) for personal/non-commercial use for only the cost of shipping (about
$20US). The distribution comes on an ISO9660-format CDROM which can be mounted and used to copy the necessary files.
Run the following script to copy the basic set of files from a SCO distribution directory mounted somewhere locally:
/usr/share/examples/emul/ibcs2/ibcs2-setup [directory]
You should now be set up for SCO binaries which only need standard shared libs.
BUGS
The information about SCO distributions may become outdated.
Attempting to a use a nameserver on the local host does not currently work due to an absurd shortcut taken by the iBCS2 network code (remem-
ber that there are no kernel sockets).
16/32/64 bit offsets may not be handled correctly in all cases.
BSD
February 8, 1998 BSD