testing SquidGuard


 
Thread Tools Search this Thread
Special Forums UNIX and Linux Applications testing SquidGuard
# 1  
Old 10-22-2008
testing SquidGuard

Hi all,

I installed squid + squidguard..

How do i do a simple test the squidguard?

i did some research and i supposed to do dry run test , but i dont understand.

Anyone can explain to me?

Do i need to type in the command below on the prompt?

echo "http://www.xxx.com 10.0.0.1/ - - GET" | squidGuard -c /tmp/test.cfg -d


What is squidGuard -c /tmp/test.cfg -d represents to?
Login or Register to Ask a Question

Previous Thread | Next Thread

2 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

testing

what is the difference between white box and black box testing? (1 Reply)
Discussion started by: areef4u
1 Replies

2. UNIX for Advanced & Expert Users

testing

what does one mean in the context of testing... UNIT TESTING & INITIAL LEVEL OF MENU TESTING (2 Replies)
Discussion started by: areef4u
2 Replies
Login or Register to Ask a Question
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)