|
|
Sponsored Content
Top Forums
Shell Programming and Scripting
Making bash script allways executable when transfer ?
Post 302979976 by MadeInGermany on Monday 22nd of August 2016 01:40:18 PM
08-22-2016
|
|
10 More Discussions You Might Find Interesting
1. AIX
Hi All:
I am a newbie.
I have shell script and bunch of java jar files and I want to give one single executable file (may be .bin).
Ex: I have test.sh, jar1.jar, jar2.jar. I have to make process.xxx
When we run "process.xxx" it will run the "test.sh" script which inturn uses jar1.jar and... (0 Replies)
Discussion started by: laxman123
0 Replies
2. UNIX for Dummies Questions & Answers
Hello,
I am very new to UNIX and I have been learning about writing scripts and making them executable. I created a script called myscript. It has three lines:
#! /bin/sh
# This is my first shell script
echo friendsjustfriends
Now I try to run it using the sh command and it works
Next I... (4 Replies)
Discussion started by: rohitx
4 Replies
3. UNIX for Dummies Questions & Answers
making a script in vi to create a shell script called wherearethey by entering the following script:
echo -n "Who are you looking for: "read userif then list=`w | grep $user | cut -c19-30` if then echo "The user $user is logged in from $list" else echo "The user $user is not logged in... (3 Replies)
Discussion started by: curtner
3 Replies
4. Shell Programming and Scripting
Guys I placed
#!path/awk -f
placed awk script
and used $1 to call 1st inputfile inside the script.
But some where I did mistake. Could you please help me run this script as executable
I forgot to mention I also used BEGIN before placing awk script. But nothing worked out.
Script
... (2 Replies)
Discussion started by: repinementer
2 Replies
5. UNIX for Dummies Questions & Answers
Hi guys, i'm trying to make a file called 'run-all-tests' executable but it is not letting me for some reason. I am presented with the following error: chmod: cannot access `./run-tests': No such file or directory
Basically i have a folder called ex3 and within that there are task folders:... (11 Replies)
Discussion started by: Shyamz1
11 Replies
6. UNIX for Dummies Questions & Answers
Hey guys, so I've been trying to write a bash script called runSorter.sh that runs an executable that also takes in some parameters and outputs the results to a text file. The executable, sorter, takes in a number parameter. I want to make it so that you can input as many number parameters into... (4 Replies)
Discussion started by: Duo11
4 Replies
7. Shell Programming and Scripting
Hello,
I have a perl program called snp_hwe.pl
I have another program called hwe_test.run which contains the following:
for file in *.inp
do
cp $file genotype_counts_c.txt
./snp_hwe.exe > $file'.res'
done
I want to change my perl program to an executable program while changing... (3 Replies)
Discussion started by: Homa
3 Replies
8. Shell Programming and Scripting
I wish to create an executable bash script that will run the following commands as root, that is, using sudo su
iptables-save | awk '/^
/ { print $1 }
/^:+ / { print $1 " ACCEPT" ; }
/COMMIT/ { print $0; }' | iptables-restoreMy first attempt at bash... (9 Replies)
Discussion started by: thixeqi
9 Replies
9. Shell Programming and Scripting
Hi all,
I'm new to Unix so just wanted some help.
I've been self learning and came accross a question online that I was trying. It is to make any shell script executable, the name of the file is to be made executable.
I would use nano and type in something like
#! /bin/bash
Chmod +x... (4 Replies)
Discussion started by: HelenaR
4 Replies
10. Shell Programming and Scripting
Is there a way to make this make itself executable?
Thanks. :-)
cat > somescript.sh << \EOF
#!/bin/bash
block_count=$(sudo tune2fs -l /dev/sda1 | awk '/^Block count:/ {print $NF}')
reserved_block_count=$(sudo tune2fs -l /dev/sda1 | awk '/^Reserved block count:/ {print $NF}')
perl -e... (4 Replies)
Discussion started by: drew77
4 Replies
LEARN ABOUT FREEBSD
ddb
DDB(8) BSD System Manager's Manual DDB(8) NAME
ddb -- configure DDB kernel debugger properties SYNOPSIS
ddb capture [-M -core] [-N -system] print ddb capture [-M -core] [-N -system] status ddb script scriptname ddb script scriptname=script ddb scripts ddb unscript scriptname ddb pathname DESCRIPTION
The ddb utility configures certain aspects of the ddb(4) kernel debugger from user space that are not configured at compile-time or easily via sysctl(8) MIB entries. To ease configuration, commands can be put in a file which is processed using ddb as shown in the last synopsis line. An absolute pathname must be used. The file will be read line by line and applied as arguments to the ddb utility. Whitespace at the beginning of lines will be ignored as will lines where the first non-whitespace character is '#'. OUTPUT CAPTURE
The ddb utility can be used to extract the contents of the ddb(4) output capture buffer of the current live kernel, or from the crash dump of a kernel on disk. The following debugger commands are available from the command line: capture [-M core] [-N system] print Print the current contents of the ddb(4) output capture buffer. capture [-M core] [-N system] status Print the current status of the ddb(4) output capture buffer. SCRIPTING
The ddb utility can be used to configure aspects of ddb(4) scripting from user space; scripting support is described in more detail in ddb(4). Each of the debugger commands is available from the command line: script scriptname Print the script named scriptname. script scriptname=script Define a script named scriptname. As many scripts contain characters interpreted in special ways by the shell, it is advisable to enclose script in quotes. scripts List currently defined scripts. unscript scriptname Delete the script named scriptname. EXIT STATUS
The ddb utility exits 0 on success, and >0 if an error occurs. EXAMPLES
The following example defines a script that will execute when the kernel debugger is entered as a result of a break signal: ddb script kdb.enter.break="show pcpu; bt" The following example will delete the script: ddb unscript kdb.enter.break For further examples, see the ddb(4) and textdump(4) manual pages. SEE ALSO
ddb(4), textdump(4), sysctl(8) HISTORY
The ddb utility first appeared in FreeBSD 7.1. AUTHORS
Robert N M Watson BUGS
Ideally, ddb would not exist, as all pertinent aspects of ddb(4) could be configured directly via sysctl(8). BSD
December 24, 2008 BSD