>.... > Nope. > In the working case everything seems just fine: > 2006-01-24 21:32:37 [11225] squidGuard 1.2.0 started (1138138357.409) > 2006-01-24 21:32:37 [11225] squidGuard ready for requests (1138138357.481) > 2006-01-24 21:32:37 [11223] squidGuard 1.2.0 started (1138138357.433) > 2006-01-24 21:32:37 [11223] squidGuard ready for requests (1138138357.482) > 2006-01-24 21:32:37 [11224] squidGuard 1.2.0 started (1138138357.435) > 2006-01-24 21:32:37 [11224] squidGuard ready for requests (1138138357.483) > 2006-01-24 21:32:37 [11221] squidGuard 1.2.0 started (1138138357.506) > 2006-01-24 21:32:37 [11221] squidGuard ready for requests (1138138357.508) > 2006-01-24 21:32:37 [11222] squidGuard 1.2.0 started (1138138357.519) > 2006-01-24 21:32:37 [11222] squidGuard ready for requests (1138138357.521) > 2006-01-24 22:11:05 [11221] squidGuard stopped (1138140665.526) > 2006-01-24 22:11:05 [11222] squidGuard stopped (1138140665.528) > 2006-01-24 22:11:05 [11223] squidGuard stopped (1138140665.530) > 2006-01-24 22:11:05 [11224] squidGuard stopped (1138140665.531) > 2006-01-24 22:11:05 [11225] squidGuard stopped (1138140665.533) > (I started with "/usr/sbin/squid -NCd 1" did some tests and closed with > CTRL-C) > > In the non-working case - cold boot with "/usr/sbin/squid" in rc.local - > you can see the results too (i.e. *nothing at all* written to > squidGuard.log). > - In the command-line case, was SQUID started from the root account ? - What's in cache.log (full log), for the failing case ? M.
