You MUST terminate an AT command line with \r and nothing else (unless you have modified ATS3, but you should not)1. To quote the V.250 specification: 5.2.1 Command line general format A command line is made up of three elements: the prefix, the body, and the termination character. The command line prefix consists of the … Read more
Your code will not work. /proc/pid/fd/0 is a link to the /dev/pts/6 file. $ echo ‘foobar’ > /dev/pts/6 $ echo ‘foobar’ > /proc/pid/fd/0 Since both the commands write to the terminal. This input goes to terminal and not to the process. It will work if stdin intially is a pipe. For example, test.py is : … Read more
How can it be that writing to physical disk is WAY faster than writing to the “screen” (presumably an all-RAM op), and is effectively as fast as simply dumping to the garbage with /dev/null? Congratulations, you have just discovered the importance of I/O buffering. 🙂 The disk appears to be faster, because it is highly … Read more
The stdout and stderr of the program being run can be logged separately. You can’t use pexpect because both stdout and stderr go to the same pty and there is no way to separate them after that. The stdout and stderr of the program being run can be viewed in near-real time, such that if … Read more
The -t option goes to how Unix/Linux handles terminal access. In the past, a terminal was a hardline connection, later a modem based connection. These had physical device drivers (they were real pieces of equipment). Once generalized networks came into use, a pseudo-terminal driver was developed. This is because it creates a separation between understanding … Read more
Granting the user to use that command without prompting for password should resolve the problem. First open a shell console and type: sudo visudo Then edit that file to add to the very end: username ALL = NOPASSWD: /fullpath/to/command, /fullpath/to/othercommand eg john ALL = NOPASSWD: /sbin/poweroff, /sbin/start, /sbin/stop will allow user john to sudo poweroff, … Read more