search for: tcgetattr

...till the SRM program just shows "None" in the com port drop down list. When I run wine SRMWIN.exe and then try and try to connect to the powercontrol the terminal output is: Code: wine SRMWIN.exe fixme:comm:set_queue_size insize 40 outsize 40 unimplemented stub err:comm:get_baud_rate tcgetattr error 'Input/output error' fixme:comm:set_queue_size insize 40 outsize 40 unimplemented stub err:comm:set_baud_rate tcgetattr error 'Input/output error' err:comm:set_baud_rate tcgetattr error 'Input/output error' err:comm:set_baud_rate tcgetattr error 'Input/output error...

...mands individually, they both work (albeit with some strange output I'd like to suppress): [tdunphy at MIAGRBISSH01V ~]$ ssh -q -t -t -t MIAGRBIORCA00V sudo -S 'cp -v /data/solr-4.3.1/zoe/etc/logback.xml /tmp/logback.xml-${i}-$(date +%Y%m%d).bak' <<EOF > secret_sauce > EOF tcgetattr: Inappropriate ioctl for device `/data/solr-4.3.1/zoe/etc/logback.xml' -> `/tmp/logback.xml--20131007.bak' [tdunphy at MIAGRBISSH01V ~]$ ssh -q -t -t -t MIAGRBIORCA00V sudo -S 'ls -l /home/tdunphy/logback.xml-${i}-$(date +%Y%m%d).bak' <<EOF > secret_sauce > EOF tcg...

...race:comm:ClearCommError handle 0xc8 cbInQue = 0 cbOutQue = 0 trace:comm:WaitCommEvent (0xc8 0x45bd3158 0x6593b8c ) fixme:comm:SetupComm insize 1024 outsize 1024 unimplemented stub trace:comm:SetCommTimeouts (0xcc,0x4069f964) trace:comm:GetCommState handle 0xcc, ptr 0x4069f978 err:comm:GetCommState tcgetattr or ioctl error 'Input/output error' trace:comm:PurgeComm handle 0xcc, flags f trace:comm:EscapeCommFunction handle 0xcc, function=6 trace:comm:EscapeCommFunction handle 0xcc, function=4 fixme:comm:SetupComm insize 1024 outsize 1024 unimplemented stub trace:comm:SetCommTimeouts (0xd0,0x4069f...

...3 port = /dev/bus/usb/002/006 upstype = 13 desc = "UPS" error: root at alhana:/etc/nut# /etc/rc.d/rc.ups start Network UPS Tools - UPS driver controller 2.6.0 Network UPS Tools - Generic contact-closure UPS driver 1.36 (2.6.0) UPS type: Repoteck RPT-800A, RPT-162A tcgetattr: Inappropriate ioctl for device Driver failed to start (exit status=1) Does this mean that the driver is not supported or am I missing something? Best regards, M. Ivanov

...add much more complexity to TSAN (to wit, additional testing failure vulnerability), while the latter will mean more (mechanical) changes to BIONIC. Currently, my thinking is that the latter, (being mechanical in nature) is preferable. - *To ENH: The same holds for calls to tcgetattr() --> ioctl(), and isatty() -> tcgetattr() --> ioctl() call chains. *TSAN intercepts tcgetattr() and ioctl(), and is not expecting recursive interceptions during them. Its not at all clear how to handle this within TSAN, especially among multiple threads. Even if a...

...Uploaded: clang+llvm-3.8.0-rc3-x86_64-linux-gnu-ubuntu-16.04.tar.xz clang+llvm-3.8.0-rc3-x86_64-linux-gnu-ubuntu-15.10.tar.xz clang+llvm-3.8.0-rc3-x86_64-linux-gnu-ubuntu-14.04.tar.xz On Ubuntu 16.04 x86_64: Failing Tests (7): MemorySanitizer :: Linux/forkpty.cc MemorySanitizer :: Linux/tcgetattr.cc MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.getmntent MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.getmntent_r MemorySanitizer-Unit :: Msan-x86_64-with-call-Test/MemorySanitizer.getmntent MemorySanitizer-Unit :: Msan-x86_64-with-call-Test/MemorySani...

...iver = apcsmart port = /dev/apcusb desc = "Main 2200 XP with battery pack" ===== This is what happens when apcsmart is executed ===== # cd /usr/libexec/nut/ # ./apcsmart -a 2200XL Network UPS Tools - APC Smart protocol driver 2.03 (2.4.3) APC command table version 2.1 tcgetattr(/dev/apcusb): Invalid argument

...n the UPS (I plan on using udev to give my UPS a proper home in /dev later). However, every time I've tried I've gotten this output from `upsdevctrl start` (the node in /dev varied each time) Network UPS Tools - UPS driver controller 2.0.3 Network UPS Tools - CyberPower driver 1.00 (2.0.3) tcgetattr(/dev/bus/usb/004/007): Inappropriate ioctl for device Driver failed to start (exit status=1) This is when I noticed something strange/unusual in my dmesg output. When I plugged in my UPS, I would get this message: usb 4-2: new low speed USB device using uhci_hcd and address 4 hiddev0: USB HID v1...

Part 2 fix for: https://bugzilla.redhat.com/show_bug.cgi?id=1842440 Actually this fix on its own should be sufficient, but probably we want the nbdkit fixes too. Note this uses actual OCaml 4.05 features! ("let open" and the Unix.tcgetattr functions). I checked that both features are available on RHEL 7's OCaml. Rich.

Dear testers, Release Candidate 3 has just been tagged [1]. Please build, test, and upload to the sftp. If there are no regressions from previous release candidates, this will be the last release candidate before the final release. Release notes can still go into the branch. Thanks again for all your work! Hans [1] http://lists.llvm.org/pipermail/llvm-branch-commits/2016-February/009866.html

...page 8) there: http://www.watfordcontrol.co.th/products/UPS/series_ae1/Catalog_A-19_A_E_engl(1999).pdf My question is, do I have to swap the TXD and RXD pins to get it working? I have tried to add the USB device address into the ups.conf and run the driver config tool thing. After a while it says: tcgetattr(/proc/bus/usb/004/002): Inappropriate ioctl for device After that I have tried the serial port, with a 1:1 cable, which didn't worked as well. The UPS has the SIC option installed (page 22 on the catalog) so maybe the invoke shutdown pin can be used. Thanks a lot Steve

On May 16, 2012, at 10:10 AM, Arnaud Quette wrote: > Author: aquette > Date: Wed May 16 14:10:40 2012 > New Revision: 3603 > URL: http://trac.networkupstools.org/projects/nut/changeset/3603 > > Log: > Final fix to the tcsetattr() / tcgetattr() issue I propose reverting this commit for now, until we work in all of the autoconf magic to detect whether the various termio bits are present in the header files. (It failed to build on AIX, Solaris sparc+intel, and HPUX.) -- Charles Lepple clepple at gmail

...tp, fail. ssh -vvvv shardik (which is a *nix box) snip snip debug1: Authentication succeeded (password). Authenticated to shardik ([192.168.0.1]:22). debug1: channel 0: new [client-session] debug3: ssh_session2_open: channel_new: 0 debug2: channel 0: send open debug1: Entering interactive session. tcgetattr: Invalid argument debug2: callback start debug2: fd 3 setting TCP_NODELAY debug3: packet_set_tos: set IP_TOS 0x10 debug2: client_session2_setup: id 0 debug2: channel 0: request pty-req confirm 1 debug1: tty_make_modes: no fd or tio debug2: channel 0: request shell confirm 1 debug2: callback done de...

...---- ---- /etc/nut/ups.conf --- [unitek] driver = megatec port = /dev/input/event3 desc = "Server" root at elsa:/dev/input# upsdrvctl -u root start Network UPS Tools - UPS driver controller 2.0.5 Network UPS Tools - Megatec protocol driver 1.5 (2.0.5) Carlos Rodrigues (c) 2003-2006 tcgetattr(/dev/input/event3): Inappropriate ioctl for device Driver failed to start (exit status=1) ---------- root at elsa:/dev/input# upsdrvctl -u root start Network UPS Tools - UPS driver controller 2.0.5 Network UPS Tools - Megatec protocol driver 1.5 (2.0.5) Carlos Rodrigues (c) 2003-2006 tcgetattr(/d...

...p, and report results to this thread. LNT is looking good on Ubuntu 14.04 x64, uploaded: clang+llvm-3.7.0-rc2-x86_64-linux-gnu-ubuntu-14.04.tar.xz The errors reported during build are: Failing Tests (17): AddressSanitizer-x86_64-linux :: TestCases/Posix/readv.cc MemorySanitizer :: Linux/tcgetattr.cc MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.gethostent MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.gethostent_r MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.getmntent MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.getmntent_r...

...-al /dev/hiddev0 crw------- 1 nut nut 180, 96 Nov 27 09:07 /dev/hiddev0 When i try to start nut i get the following : # upsdrvctl start Network UPS Tools - UPS driver controller 2.2.0- Network UPS Tools (version 2.2.0-) - APC Smart protocol driver Driver version 1.99.8, command table version 2.0 tcgetattr(/dev/hiddev0): Invalid argument Driver failed to start (exit status=1) Thanks in advance if someone can help ! -- Guillaume Vachon (RHCE, CLP10, CTT+, CNI) Conseiller en TI, Formateur Infoglobe, http://infoglobe.ca 1963, Frank-Carrel, 201 - Qu?bec, QC G1N 2E6 T?l?phone : 418.681.2929 #123

Hello All, Doing a make distprep doesn't seem to work anymore: $ make -f Makefile.in distprep make: @SH@: Command not found make: *** [catman-do] Error 127 I've seen this on AIX & Redhat (gnu make) and Solaris (native make). I suspect this occurs on most platforms. Is this still the recommended way of autoreconf'ing CVS releases for building? -Daz.

...signo); + /* restore the terminal to its original state */ + if (tcsetattr(fileno(stdin), TCSADRAIN, &_saved_tio) == -1) + perror("tcsetattr"); + _exit(1); } @@ -218,6 +225,11 @@ extern char *optarg; extern int optind; + if (tcgetattr(fileno(stdin), &_saved_tio) == -1) { + perror("tcgetattr"); + return 0; + } + __progname = ssh_get_progname(argv[0]); args.list = NULL;

hello short description: ssh client sends a wrong all-zero terminal info when requesting forced pseudo-terminal allocation while stdin is not a terminal. sshd then sets the terminals ospeed to 0 because it receives this information from the client. on solaris this means that the pseudo-terminal is closed and output of any remote command is dropped. longer description: what we're doing is

...text/binary protocol UPS driver 0.25 (2.4.3) Warning: This is an experimental driver. Some features may not function correctly. 0.000000 send_to_all: SETINFO driver.parameter.port "/dev/iDowell" 0.000064 debug level is '16' 0.011711 Trying binary protocol... 0.011745 tcgetattr(/dev/iDowell): Inappropriate ioctl for device ============================================= with microdowell I get: ============================================= # /lib/nut/microdowell -DDDDDDDDDDDDDDDD -a iDowell Network UPS Tools - MICRODOWELL UPS driver 0.01 (2.4.3) 0.000000 send_to_all: SET...