Your problem is this line:
To the shell it means: test ([]) the variable FILECOUNT for existence and if it has a value, and redirect any output to the file named '2' (> 2). If you're using the single bracket form of the tests, you'll have to use
-gt instead of >
-lt instead of <
-ge instead of >=
-le instead of <=
-ne instead of !=
You can get a list of all test operators by looking at the man page of test.
---------- Post updated at 09:26 ---------- Previous update was at 09:21 ----------
@dennis.jacob: the parameter '-1' to ls won't change anything. If ls detects that output does not go to a terminal it automatically switches to single-column mode. You can easily test that by running
in any directory.
Yes pludi, Its my mistake. Thank you for pointing that.
I'm writing a script to find the oldest file in a directory. I know this can be done by using ls -rt | tail -1 but these are rather large directories and that can be somewhat slow since the script will be running constantly.
Are there any other ways to do this that would be faster? I looked to... (2 Replies)
Hi all,
I need your assistance in removing the oldest file in a directory.
I posted the same thread 3 days back and I got the following answer
ls -1 -t | tail -1 | xargs rm
which is not covering the case when there are directories older than the oldest file.
So, could you please... (2 Replies)
I am using a bash script to perform some automated maintenance on files in a directory. When I run the script using $sh -x script.sh <directory> the script works fine. It sets the variable to the oldest file, and continues on. However when I run the script like this $./script.sh <directory>, it... (5 Replies)
Hi all,
I am a newbie to scripting and I need your help regarding finding the oldest file in a particular directory. My intention is to remove that oldest file.
Are there any options available with the "find" command to do this..
Thanks in advance for your help
Pavan (4 Replies)
I am trying to determine the oldest and most recent files in a huge directory. I am using an ls -tr statement outside my find statement. The directory is too big and I am getting an "arg list too long" error. Is there something I can put in my find statement that doesn't create a list to... (2 Replies)
The `bash` below uses the oldest folder in the specified directory and logs it. The goes though an analysis process and creates a log. My problem is that if there are 3 folders in the directory folder1,folder2,folder3, the bash is using folder2 for the analysis eventhough folder1 is the oldest... (0 Replies)
In the bash below the oldest folder in a directory is selected. If there are 3folders in the directory /home/cmccabe/Desktop/NGS/test and nothing is done to them (ie. no files deleted, renamed) then the bash correctly identifies f1 as the oldest. However, if something is done to the folder then... (4 Replies)
Discussion started by: cmccabe
4 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)