10-28-2016
Repeating what has been said before doesn't really help. HOW do you produce above output? Show the script and related data, e.g. input files.
10 More Discussions You Might Find Interesting
1. BSD
I'm trying to understand what is happening.
The "setup".
System running OpenBSD 3.3
Connect to the system using PuTTy or with the SSH.COM SSH client, issue a DF command.
First line that comes back is:
Filesystem 1K-blocks Used Avail Capacity Mounted on
When I connect the the... (13 Replies)
Discussion started by: woodstone
13 Replies
2. Shell Programming and Scripting
Hi,
I have a script that's being called via a crontab which is a wrapper script that creates a log for the script that gets executed. Within the script that gets executed, it also run's subscripts. I've been able to get everything to work .. but the issue is one of the subscript that goes out... (4 Replies)
Discussion started by: primp
4 Replies
3. Shell Programming and Scripting
Hi All,
When starting an SSH tunnel, piped output 'hangs' (on AIX) :
ssh -Nf -Llocalhost:22000:server:22 proxy | cat -vet -
... hangs ...
Does anybody know how to prevent this?
Of course, in my script I don't use the tunnel as I do in the example above. In my script the call to ssh is... (7 Replies)
Discussion started by: whbos
7 Replies
4. Shell Programming and Scripting
Hello;
Am trying to generate runaway proc report using ssh thusly:
===================
ssh -t -t $BOX 'TERMINAL="vt100" top -d1 -h -n 10' >> $FILE
.
.
cat $FILE | mail -s "Latest Top `date`" $MAIL_TO
====================
But the output to e-mail comes out rather garbled ..
Any ideas... (1 Reply)
Discussion started by: delphys
1 Replies
5. Shell Programming and Scripting
Hello;
Am trying to correct the formatting of tail output over ssh.
Using the following code:
echo "" > $FILE
for BOX in $SERVERS
do
echo "Processing on $BOX" |tee -a $FILE
echo "===============================" >> $FILE
sudo ssh $BOX 'TERMINAL="vt100" /usr/bin/sh -s' <... (2 Replies)
Discussion started by: delphys
2 Replies
6. Shell Programming and Scripting
Hey Guys,
i have a script that generates logs at our isilon storage.
The part of the script is to geneate logs and grep its name:
VAR=`ssh -o UserKnownHostsFile=/dev/null root@XXX isi_gather_info | grep -i "Package:" | awk '{ print $2 }'` Now , while this is run, i do not see the status of... (2 Replies)
Discussion started by: anshulsahdev
2 Replies
7. Shell Programming and Scripting
The code below works ok, however; I need to output the results to a local variable
the_path="/mnt/back/hang"
ssh -T -i /home/buddy/.ssh/id_rsa buddy@ginger << EOF
find ${the_path} -name "*.jpg" | wc -l > ## output to local variable
exit
EOF (3 Replies)
Discussion started by: squrcles
3 Replies
8. Shell Programming and Scripting
Hi All,
I am using below command in a shell script.
ssh -q RemoteUser@RemoteServer "/export/sctipt/test.ksh"
It is executing succesfully but the below is the output getting displayed.
tset: standard error: Invalid argument
Can you please help me in understanding below.
... (8 Replies)
Discussion started by: Girish19
8 Replies
9. Shell Programming and Scripting
Hi everyone, after about 2 days of scratching my head on this one, I'm finally ready to punt this and ask for some actual help. Here's the situation. We have 1 server, that runs multiple VM's. To gain access to those VM's we ssh from host01 to the other vm hosts. For example when we first log... (4 Replies)
Discussion started by: Lost in Cyberia
4 Replies
10. Shell Programming and Scripting
Hi Folks,
I'm currently trying to read several values into different variables.
Actually, what I'm doing works, but I get an error message.
My attempts are:
read strCPROC strIPROC strAPROC <<<$(ssh -n -T hscroot@$HMC "lshwres -r proc -m $strIDENT --level sys -F \"configurable_sys_proc_units... (11 Replies)
Discussion started by: NKaede
11 Replies
LEARN ABOUT MOJAVE
osacompile
OSACOMPILE(1) BSD General Commands Manual OSACOMPILE(1)
NAME
osacompile -- compile AppleScripts and other OSA language scripts
SYNOPSIS
osacompile [-l language] [-e command] [-o name] [-d] [-r type:id] [-t type] [-c creator] [-x] [-s] [-u] [-a arch] [file ...]
DESCRIPTION
osacompile compiles the given files, or standard input if none are listed, into a single output script. Files may be plain text or other
compiled scripts. The options are as follows:
-l language
Override the language for any plain text files. Normally, plain text files are compiled as AppleScript.
-e command
Enter one line of a script. Script commands given via -e are prepended to the normal source, if any. Multiple -e options may be given
to build up a multi-line script. Because most scripts use characters that are special to many shell programs (e.g., AppleScript uses
single and double quote marks, ``('', ``)'', and ``*''), the command will have to be correctly quoted and escaped to get it past the
shell intact.
-o name
Place the output in the file name. If -o is not specified, the resulting script is placed in the file ``a.scpt''. The value of -o
partly determines the output file format; see below.
-x Save the resulting script as execute-only.
The following options are only relevant when creating a new bundled applet or droplet:
-s Stay-open applet.
-u Use startup screen.
-a arch
Create the applet or droplet for the specified target architecture arch. The allowable values are ``ppc'', ``i386'', and ``x86_64''.
The default is to create a universal binary.
The following options control the packaging of the output file. You should only need them for compatibility with classic Mac OS or for cus-
tom file formats.
-d Place the resulting script in the data fork of the output file. This is the default.
-r type:id
Place the resulting script in the resource fork of the output file, in the specified resource.
-t type
Set the output file type to type, where type is a four-character code. If this option is not specified, the creator code will not be
set.
-c creator
Set the output file creator to creator, where creator is a four-character code. If this option is not specified, the creator code will
not be set.
If no options are specified, osacompile produces a Mac OS X format script file: data fork only, with no type or creator code.
If the -o option is specified and the file does not already exist, osacompile uses the filename extension to determine what type of file to
create. If the filename ends with ``.app'', it creates a bundled applet or droplet. If the filename ends with ``.scptd'', it creates a bun-
dled compiled script. Otherwise, it creates a flat file with the script data placed according to the values of the -d and -r options.
EXAMPLES
To produce a script compatible with classic Mac OS:
osacompile -r scpt:128 -t osas -c ToyS example.applescript
SEE ALSO
osascript(1), osalang(1)
Mac OS X November 12, 2008 Mac OS X