Did you test on your system, what did those commands return ?
In my test (with debian 5) it should be :
And this command should be translated to : find all numbers starting with 12
Can any one tell me what is the importance of '/dev' directory in unix. Is there any possibility to get 'root' by using the files stored in this directory.
Beleive me this is not for any hacking purpose. just for learning.
Hopes a detail reply. thak you (1 Reply)
Is there any importance of LS length in DB exchange packet of OSPF protocol as its should be always be 20 bytes. Is this length to be ignored (2 Replies)
I have written a script for sending automated email, reporting the running status of a cron scheduled work. Now, the issue is, my Project Manager wants, the mail should be received with HIGH IMPORTANCE.
How can I do that, kindly anybody explain.
Thank you so much. (3 Replies)
Hi
When an entry will be made to the file /var/mail/<user-id> .
I have 100 scripts under a specific user id(dgircc) in cron .SO inrder to check the whether the script has sucessfully run or not and if not to generate an email
if i mention the code like
#!/bin/ksh -p
2 fsize=`ls -lrt... (0 Replies)
Hi,
I have multiple list which is arranged by order of importance. I need to do sorting on these lists based on the last name of the user(initial), if user name does not have initial then first name is initial . Important thing is that the last name in the list is important. If there is two or... (1 Reply)
Hi All,
Can you please help me in understanding the importance of -depth of find.
I am trying to execute below code.find . -mtime +5 -name "*" -depth -exec ls -l {} \;
But it is throwing below error.find: warning: you have specified the -depth option after a non-option argument -mtime,... (2 Replies)
Discussion started by: Girish19
2 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)