01-07-2003
That sounds like flow control. Characters are arriving too fast for the driver to read them. Are you using a real terminal? If you're using a network connection, are you using rlogin? If so switch to telnet and repeat your test. Bear in mind that even if flow control is working properly, it is not directly connected to you. All it can do is beep and hope that you stop typing.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
when sending the contents of a ascii file to the body of an email then sending it off. it seems sendmail is breaking up the lines with a "!" thus ruining the data. Has this ever happened to anyone?
i am guessing there is a line buffer limit in either the mail command or in sendmail itself.
... (3 Replies)
Discussion started by: Optimus_P
3 Replies
2. Shell Programming and Scripting
Hi Friends,
I am having a funny problem with grep. When I run
grep 'expr' file.txt
things work fine. But when try to get the line number using the -n option, i.e,
grep -n 'expr' file.txt
I get a message, "grep: 0652-226 Maximum line length of 2048 exceeded."
If the line has more than... (3 Replies)
Discussion started by: hnhegde
3 Replies
3. Shell Programming and Scripting
Hi,
I have 13jobs waiting in a printer queue.I am try to get the status and number of jobs using lpstat but i cant see any job is waiting in queue.i think those jobs are in printer buffer.is there any way to get the status of printer buffer too using unix command.please correct me if i am wrong. i... (1 Reply)
Discussion started by: sagii
1 Replies
4. UNIX for Advanced & Expert Users
Hello All,
I am trying to search one pattern across a file and then print it. But i need to delimit the search per line to 2 occurrences. How do i do that?
Regards. (9 Replies)
Discussion started by: Linuxee
9 Replies
5. Shell Programming and Scripting
Hi
I have many problems with a script. I have a script that formats a text file but always prints the same error when i try to execute it
The code is that:
{
if (NF==17){
print $0
}else{
fields=NF;
all=$0;
while... (2 Replies)
Discussion started by: fate
2 Replies
6. Programming
Is there any stabdard limitation on size of a code line in C code?
I am interesting in UNIX limitation, particulary on SUN.
Thanks! (8 Replies)
Discussion started by: alex_5161
8 Replies
7. UNIX for Dummies Questions & Answers
Hi,
From inside Vim, I'm looking for a way to use the contents of the current buffer, pass it to an external executable, and then return the output from the executable into a new Vim buffer.
I know that I can do something like %!<executable>, but that will overwrite the contents of the... (3 Replies)
Discussion started by: konfushus
3 Replies
8. Shell Programming and Scripting
Hi
I would just like to ask if there is a way for UNIX to ignore/overcome the 255 character limit of the command line?
My problem is that I have a really long line of text from a file (300+ bytes) which i have to "echo" and process by adding commands like "sed" to the end of the line, like... (5 Replies)
Discussion started by: agentgrecko
5 Replies
9. Programming
Hey guys, can help me out with this?
How do i limit output for xml to 50 character?
i tried *below* but doesnt work, it still print more than 50 characters.
Thanks in advance
printf "%-50s", "$testline\n"; (4 Replies)
Discussion started by: Nick1097
4 Replies
10. UNIX for Beginners Questions & Answers
Hello Guys,
Is there a single line archive command to zip or tar log files which is larger than certain size limit ?
Do let me know if there is any.
Thanks (7 Replies)
Discussion started by: UnknownGuy
7 Replies
PTS(4) BSD Kernel Interfaces Manual PTS(4)
NAME
pts -- pseudo-terminal driver
DESCRIPTION
The pts driver provides support for a device-pair termed a pseudo-terminal. A pseudo-terminal is a pair of character devices, a master
device and a slave device. The slave device provides to a process an interface identical to that described in tty(4). However, whereas all
other devices which provide the interface described in tty(4) have a hardware device of some sort behind them, the slave device has, instead,
another process manipulating it through the master half of the pseudo-terminal. That is, anything written on the master device is given to
the slave device as input and anything written on the slave device is presented as input on the master device.
The following ioctl(2) calls apply only to pseudo-terminals:
TIOCPKT Enable/disable packet mode. Packet mode is enabled by specifying (by reference) a nonzero parameter and disabled by specifying
(by reference) a zero parameter. When applied to the master side of a pseudo-terminal, each subsequent read(2) from the termi-
nal will return data written on the slave part of the pseudo-terminal preceded by a zero byte (symbolically defined as
TIOCPKT_DATA), or a single byte reflecting control status information. In the latter case, the byte is an inclusive-or of zero
or more of the bits:
TIOCPKT_FLUSHREAD whenever the read queue for the terminal is flushed.
TIOCPKT_FLUSHWRITE whenever the write queue for the terminal is flushed.
TIOCPKT_STOP whenever output to the terminal is stopped a la '^S'.
TIOCPKT_START whenever output to the terminal is restarted.
TIOCPKT_DOSTOP whenever VSTOP is '^S' and VSTART is '^Q'.
TIOCPKT_NOSTOP whenever the start and stop characters are not '^S/^Q'.
While this mode is in use, the presence of control status information to be read from the master side may be detected by a
select(2) for exceptional conditions.
This mode is used by rlogin(1) and rlogind(8) to implement a remote-echoed, locally '^S/^Q' flow-controlled remote login with
proper back-flushing of output; it can be used by other similar programs.
TIOCGPTN Obtain device unit number, which can be used to generate the filename of the pseudo-terminal slave device. This ioctl(2) should
not be used directly. Instead, the ptsname(3) function should be used.
TIOCPTMASTER Determine whether the file descriptor is pointing to a pseudo-terminal master device. This ioctl(2) should not be used
directly. It is used to implement routines like grantpt(3).
FILES
The files used by this pseudo-terminals implementation are:
/dev/pts/[num] Pseudo-terminal slave devices.
DIAGNOSTICS
None.
SEE ALSO
posix_openpt(2), grantpt(3), ptsname(3), pty(4), tty(4)
HISTORY
A pseudo-terminal driver appeared in 4.2BSD. In FreeBSD 8.0, it was replaced with the pts driver.
BSD
August 20, 2008 BSD