Sponsored Content
Full Discussion: Plink wait problem
Special Forums Windows & DOS: Issues & Discussions Plink wait problem Post 303001369 by Corona688 on Wednesday 2nd of August 2017 11:51:04 AM
Old 08-02-2017
If it really is waiting on keyboard, have you tried just
Code:
plink < textfile

? Windows isn't smart enough to tell the difference between textfile and terminal, so it might actually work as a "fake keyboard".
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

I/O wait Problem

When running top, I notice a bit more I/O wait time than usual. Is there a tool or piece of software out there that can me help evaluate the performance of these operations on my machine? Thanks! (5 Replies)
Discussion started by: unavb
5 Replies

2. Shell Programming and Scripting

Need to execute 2 scripts, wait, execute 2 more wait, till end of file

:cool: I need to execute a shell script to do the following: cat a file run two back ground processes using the first two values from the file wait till those background processes finish run two more background processes using the next two values from the file wait till those background... (1 Reply)
Discussion started by: halo98
1 Replies

3. UNIX for Dummies Questions & Answers

Plink problem....only works if passwd is in the script

I have a one line bat script run off a XP machine that tar's and compresses some files from a Sol 8 box. It goes something like this (a bit simplified).... plink -pw <passwd> user@host "tar -cvf - -C / tmp/a_file | compress " > a_file.tar.Z So this works....and it's worked many times. But now... (3 Replies)
Discussion started by: Yinzer955i
3 Replies

4. Shell Programming and Scripting

wait command - cat it wait for not-chile process?

Did not use 'wait' yet. How I understand by now the wait works only for child processes, started background. Is there any other way to watch completion of any, not related process (at least, a process, owned by the same user?) I need to start a background process, witch will be waiting... (2 Replies)
Discussion started by: alex_5161
2 Replies

5. Shell Programming and Scripting

wait problem

Hello, I have been trying to figure out why the wait isnt waiting for the sleep process to complete till now and have found out that since sleep runs as different process and not a child process the wait isnt waiting. script: cat test|while read i do echo $i sleep 30 & done wait ps... (4 Replies)
Discussion started by: wannalearn
4 Replies

6. Shell Programming and Scripting

plz, i wait your help, AWK problem

I have tracefile of three nodes (0 , 1 and 2 ) as follows: + 0.02 0 1 tcp 40 ------- 1 0.0 2.0 0 0 - 0.02 0 1 tcp 40 ------- 1 0.0 2.0 0 0 + 0.02 2 1 tcp 40 ------- 2 2.1 0.1 0 1 - 0.02 2 1 tcp 40 ------- 2 2.1 0.1 0 1 r 0.025032 0 1 tcp 40 ------- 1 0.0 2.0 0 0 + 0.025032 1 2 tcp 40 -------... (11 Replies)
Discussion started by: ASAADAOUI
11 Replies

7. HP-UX

echo "selall;info;wait;infolog" | /usr/sbin/cstm problem

Hello, On a HP-UX 10.20 server I've executed something similar to this command: # echo 'selall;info;wait;infolog;view;done' | /usr/sbin/cstm But it returns sometype of "argument list too long" error. I suppose there is a way to fix it by using xargs but I can't figure it out. Any... (7 Replies)
Discussion started by: asanchez
7 Replies

8. Shell Programming and Scripting

calling a shell script in background and wait using "wait" in while loop

Hi, I am facing a strange issue, when i call a script from my while loop in background it doesnt go in background, despite the wait i put below the whil loop it goes forward even before the process put in background is completed. cat abc.txt | while read -u4 line do #if line contains #... (2 Replies)
Discussion started by: mihirvora16
2 Replies

9. Shell Programming and Scripting

[SOLVED] Problem in wait statement

Iam having a script which is used to load users and dumpfile in any given schema.Iam trying to autolog the script and have added two fucntion in it. function init_stdout_redirect { OUT_LOG=$1 OUT_PIPE=$(mktemp -u) # Create the output pipe mkfifo $OUT_PIPE # Save stdout and... (15 Replies)
Discussion started by: Vikram_Tanwar12
15 Replies

10. Shell Programming and Scripting

Problem with output file plink GWAS

hi, Can anybody help me about the odd output file yielded by the following command: plink --noweb --allow-no-sex --bfile input_file --assoc --adjust --out output_file In fact, I'd like to perform a simple Bonferroni basic association test, and I obtains the following output file (extract... (1 Reply)
Discussion started by: boro82
1 Replies
VI(1)							      General Commands Manual							     VI(1)

NAME
vi, ki, xi - instruction simulators SYNOPSIS
vi [ textfile ] vi pid ki [ textfile ] ki pid xi [ textfile ] xi pid DESCRIPTION
Vi simulates the execution of a MIPS binary in a Plan 9 environment. It has two main uses: as a debugger and as a statistics gatherer. Programs running under vi execute about two hundred times slower than normal--but faster than single stepping under db. Ki and xi are sim- ilar to vi but interpret SPARC and ATT3210 binaries. The following discussion refers to vi but applies to the others as well. Vi will simulate the execution of a named textfile. It will also make a copy of an existing process with process id pid and simulate its continuation. As a debugger vi offers more complete information than db(1). Tracing can be performed at the level of instructions, system calls, or function calls. Vi allows breakpoints to be triggered when specified addresses in memory are accessed. A report of instruction counts, load delay fills and distribution is produced for each run. Vi simulates the CPU's caches and MMU to assist the optimization of compilers and programs. The command interface mirrors the interface to db; see db(1) for a detailed description. Data formats and addressing are compatible with db except for disassembly: vi offers only MIPS (db -mmipsco) mnemonics for machine instructions. Ki offers both Plan 9 and Sun SPARC for- mats. Several extra commands allow extended tracing and printing of statistics: $t[0ics] The t command controls tracing. Zero cancels all tracing options. i Enable instruction tracing c Enable call tracing s Enable system call tracing $i[itsp] The i command prints statistics accumulated by all code run in this session. i Print instruction counts and frequency. p Print cycle profile. t (Vi only) Print TLB and cache statistics. s Print memory reference, working set and size statistics. :b[arwe] Vi allows breakpoints to be set on any memory location. These breakpoints monitor when a location is accessed, read, written, or equals a certain value. For equality the compared value is the count (see db(1)) supplied to the command. SOURCE
/sys/src/cmd/vi etc. SEE ALSO
nm(1), db(1) BUGS
The code generated by the compilers is well supported, but some unusual instructions are unimplemented. Some Plan 9 system calls such as rfork cause simulated traps. The floating point simulation makes assumptions about the interpreting machine's floating point support. The floating point conversions performed by vi may cause a loss of precision. VI(1)
All times are GMT -4. The time now is 05:02 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy