If your folder really does have *'s in it, any use of the folder name unquoted will try and expand these *'s into other filenames. So it could be a bug in the script rather than shc.
Hi Masters,
Iam new to this Forum and this is my first post.
My question is:
I've some datafiles belongs the type (A, B, C) in the location 'export/home/lokiman '
dataA1.txt
dataB28.txt
dataC35.txt
1) I've to check the read permission for each file, if it not there then I've to... (1 Reply)
Hi,
No need to say I'm new to unix shell scripting.
I have a very simple script that goes this way:
for datos in `ls -rt $UNXLOG/26-Jan*`
do
export arch=`echo $datos |cut -d, -f1`
if
then
export linea1=`grep Debut ${arch}`
export horatot=`echo $linea1 |cut -d' ' -f5`
... (7 Replies)
Greetings, using ksh on Solaris, I am trying to identify the current version of a package installed on multiple servers using if statement in a precursor to upgrading.
I have searched the forums and have found many hits, reviewed 3 pages and have tried the different variations noted there. Also... (3 Replies)
Im trying to check if a series of directory exists and if not create them, and am having issues. All the instances of test return with the error "test:
#!/bin/bash
location_Parent=~/Documents/sight_of_sound
location_IMG=~/Documents/Sight_of_sound/IMG
location_AUD=~/Documents/Sight_of_sound/AUD... (4 Replies)
Hi, im asking for help with the next script:
echo ^;
then
if
then
printf "\033
query1.sh:
export TERM=vt100
export ORACLE_TERM=at386
export ORACLE_HOME=/home_oracle8i/app/oracle/product/8.1.7
export ORACLE_BASE=/home_oracle8i/app/oracle
export... (8 Replies)
Please can you help me understand the significance of providing arguments under sh -s in
> ssh -qtt ${user}@${host} "sh -s "${version}"" < test.sh (4 Replies)
EDIT: Resolved
Resolved by changing the first line to bash rather than csh, does bash and csh treat the brackets differently?
Hi all,
I'm doing to some basic stuff to teach myself "if"
I've written the following:
#!/bin/csh
echo "This script checks for the test file"
... (1 Reply)
Discussion started by: Meshuggener
1 Replies
LEARN ABOUT DEBIAN
go-test
GO-TEST(1) General Commands Manual GO-TEST(1)NAME
go - tool for managing Go source code
SYNOPSIS
go test [-c] [-i] [ build flags ] [ packages ] [ flags for test binary ]
DESCRIPTION
"Go test" automates testing the packages named by the import paths. It prints a summary of the test results in the format:
ok archive/tar 0.011s
FAIL archive/zip 0.022s
ok compress/gzip 0.033s
...
followed by detailed output for each failed package.
"Go test" recompiles each package along with any files with names matching the file pattern "*_test.go". These additional files can con-
tain test functions, benchmark functions, and example functions. See go-testfunc(7) for more.
By default, go test needs no arguments. It compiles and tests the package with source in the current directory, including tests, and runs
the tests.
The package is built in a temporary directory so it does not interfere with the non-test installation.
OPTIONS
In addition to the build flags, the flags handled by 'go test' itself are:
-c Compile the test binary to pkg.test but do not run it.
-i Install packages that are dependencies of the test. Do not run the test.
The test binary also accepts flags that control execution of the test; these flags are also accessible by 'go test'. See go-testflag(7)
for details.
For more about build flags, see go-build(1).
For more about specifying packages, see go-packages(7).
SEE ALSO go-build(1), go-vet(1).
AUTHOR
This manual page was written by Michael Stapelberg <stapelberg@debian.org>, for the Debian project (and may be used by others).
2012-05-13 GO-TEST(1)