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
UBT(4) BSD Kernel Interfaces Manual UBT(4)
NAME
ubt -- USB Bluetooth driver
SYNOPSIS
ubt* at uhub? port ? configuration ? interface ?
DESCRIPTION
The ubt driver provides support for USB Bluetooth dongles to the Bluetooth protocol stack.
USB Bluetooth dongles provide two interfaces, both of which the ubt driver claims. The second interface is used for Isochronous data and
will have several alternate configurations regarding bandwidth consumption, which can be set using the hw.ubtN.config sysctl(8) variable.
The number of alternate configurations is indicated by the value in the hw.ubtN.alt_config variable, and the isoc frame size for the current
configuration is shown in the hw.ubtN.sco_rxsize and hw.ubtN.sco_txsize variables.
By default, configuration 0 is selected, which means that no bandwidth is used on the Isochronous interface and no SCO data can be sent.
Consult the Bluetooth USB specification at https://www.bluetooth.org/ for complete instructions on setting bandwidth consumption. The fol-
lowing extract may be useful as a general guidance though details may differ between manufacturers.
0 No active voice channels
1 One voice channel with 8-bit encoding
2 Two voice channels with 8-bit encoding, or one voice channel with 16-bit encoding.
3 Three voice channels with 8-bit encoding
4 Two voice channels with 16-bit encoding
5 Three voice channels with 16-bit encoding
SEE ALSO
bluetooth(4), uhub(4), sysctl(8)
HISTORY
This ubt device driver was originally a character device written by David Sainty and Lennart Augustsson. It was rewritten to support socket
based Bluetooth access for NetBSD 4.0 by Iain Hibbert.
CAVEATS
Isochronous data is seemingly not well supported over USB in the current system and to get SCO working, you may have to calculate the SCO
packet size that the stack will use. This is the sco_mtu value reported by the btconfig(8) command, and when combined with the SCO header (3
bytes) should fit exactly into an integer number of Isochronous data frames where the frame size is indicated by the 'hw.ubtN.sco_txsize'
sysctl variable.
For example: I want one voice channel (which is all that is supported, for now) so am using configuration #2, with a frame length of 17
bytes. This gives possible values of:
(17 * 1) - 3 = 14
(17 * 2) - 3 = 31
(17 * 3) - 3 = 48
(17 * 4) - 3 = 65
(17 * 5) - 3 = 82
etc.
btconfig(8) shows the maximum SCO payload as 64 bytes, so I am using the next smaller size of 48, to minimize the overhead of the 3 header
bytes.
The SCO packet size can be changed using the 'scomtu' option to btconfig(8).
The failure mode is that the USB Bluetooth dongle locks up though generally removal/reinsertion will clear the problem.
BUGS
The Isochronous configuration can only be changed when the device is not marked up.
BSD
August 27, 2006 BSD