I am having trouble running a .sh file. The code 'x=${file_name:0:$z-11}' is giving me a bad substitution error. However when I run in BASH it works. Thing is when this goes to production the .sh will not be running in BASH. Is there a way to substring a string not in BASH or a way to invoke... (2 Replies)
I'm trying to use unison from bash on windows with cygwin. I don't know if this is a cygwin question, bash question or unison question. Since I always get reprimanded by the cygwin mailing list for assuming it is a cygwin problem, I'll assume it is a bash question.
The following commands work... (7 Replies)
Hello,
So my knowledge of bash scripting is not that great and I have been trying to solve this problem on my own for awhile to no avail.
Here's the error I get when running it with an OS that uses bash 3.2.x:
testagain.sh: line 10: *-1: syntax error: operand expected (error token is... (2 Replies)
I am working with a sh script on a solaris 9 zone (sol 10 host) that grabs information to build the configuration command line. the variables Build64, SSLopt, CONFIGopt, and CC are populated in the script. the script includes
CC=`which gcc`
CONFIGopt=' --prefix=/ --exec-prefix=/usr... (8 Replies)
Greetings, I have a C-program that is made to implement a hidden Markov model on an input file. The program is very memory intensive.
I've installed it on my local server where I have an account and it compiles fine. The way they have the server set up is that you can either work... (1 Reply)
Hello,
i have cronjob:
crontab -l
* * * * * pkill -f domexpcheck;sh /root/dom/domexpcheck.sh
it runs:
/var/log/cron
Mar 25 12:11:01 vps crond: (root) CMD (pkill -f domexpcheck;sh /root/dom/domexpcheck.sh)
but somehow script dont run properly via cronjob. But when i execute cronjob... (7 Replies)
Hi, I've got a Bash backup script I'm trying to run on a directory via a cron job nightly. If I ssh in and run the script manually it works flawlessly. If I set up the cron to run evertything is totally messed up I don't even know where to begin.
Basically the path structure is
... (6 Replies)
I ran this script yesterday (in the background)
/usr/bin/nohup myfilelocation/myscriptname.sh &
the script worked perfectly.
i ran it today (also in the background) and just sat there. So i killed it and ran it normally and it worked perfectly.
Anyone suggest why it just sat there and... (8 Replies)
The below command moves all the .vcf files into the directory.
cp /home/cmccabe/Desktop/test/vcf/overall/stats/*.vcf /home/cmccabe/Desktop/NGS/annovar
When I use a bash wrapper the target.txt gets created but the text files do not get copied. All the paths are the same, but not sure why... (2 Replies)
Hi; problem may be obvious, simple but I have to say it is somehow not easy to locate the issue.
I am doing some word extracting from multiline text.
Interacting in CLI seems to work without issues. First step is to add multiline text to a variable.
expect1.1>
expect1.1> set... (2 Replies)
Discussion started by: aldowski
2 Replies
LEARN ABOUT DEBIAN
getc_putc
getc_putc(8) System Manager's Manual getc_putc(8)NAME
getc_putc - program to test hard drive performance.
SYNOPSIS
getc_putc [-d dir] [-s size(KiB)] [-m machine-name] [-u uid-to-use:gid-to-use] [-g gid-to-use]
DESCRIPTION
This manual page documents briefly the getc_putc, program.
This is a simple adjunct to the bonnie++ benchmark. It is used to test various ways of doing IO one byte at a time, usually you don't need
to do enough of this for it to be a performance issue for it to matter much which way you do it. But sometimes it's necessary (for example
whan parsing IO from a terminal and then launching another process which will take over all IO, such as a simple shell).
The real benefits of this are to help settle some arguements about the performance of such things, and to educate novices about how bad
per-byte IO really is.
OPTIONS
For getc_putc every option is of the form of a hyphen followed by a letter and then the next parameter contains the value.
-d the directory to use for the tests.
-s the size of the file for byte IO performance measured in kilobytes. NB You can specify the size in mega-bytes if you add 'm' to the
end of the number.
The default for this test is to test with a 40MiB file. Of the file only 1/32 of it will be used for write() and read() system
calls (anything else takes too long), and only 1/4 of it will be used for locked getc() and putc().
-m name of the machine - for display purposes only.
-u user-id to use. When running as root specify the UID to use for the tests. It is not recommended to use root, so if you really
want to run as root then use -u root. Also if you want to specify the group to run as then use the user:group format. If you spec-
ify a user by name but no group then the primary group of that user will be chosen. If you specify a user by number and no group
then the group will be nogroup.
-g group-id to use. Same as using :group for the -u parameter, just a different way to specify it for compatibility with other pro-
grams.
-q quiet mode. If specified then some of the extra informational messages will be suppressed. Also the csv data will be the only output
on standard out and the plain text data will be on standard error. This means you can run getc_putc -q >> file.csv to record your
csv data.
OUTPUT
The primary output is plain-text in 80 columns which is designed to fit well when pasted into email and which will work well with Braille
displays.
The second type of output is CSV (Comma Seperated Values). This can easily be imported into any spread-sheet or database program.
For every test the result is a speed in KiB/s. I do not display the CPU time because it presumably is 99% of the power of a single CPU (or
something very close to that).
AUTHOR
This program, it's manual page, and the Debian package were written by Russell Coker <russell@coker.com.au>.
The documentation, the Perl scripts, and all the code for testing the creation of thousands of files was written by Russell Coker, but the
entire package is under joint copyright with Tim Bray.
SIGNALS
Handles SIGINT and does a cleanup (which may take some time), a second SIGINT or a SIGQUIT will cause it to immidiately die.
SIGXCPU and SIGXFSZ act like SIGINT.
Ignores SIGHUP.
AVAILABILITY
The source is available from http://www.coker.com.au/bonnie++ .
See http://etbe.coker.com.au/category/benchmark for further information.
SEE ALSO
bonnie++(8), zcav(8)getc_putc(8)