Mark Elsen wrote:
>>....
>>[root@localhost mark]# sudo -u squid /usr/sbin/squid -NCd 1
>>...
>>
>>
>
> That's not the way to go, and not what I asked.
> You need to make sure that the one who is defined
> as
>
> cache_effective_user
>
> can execute ..../squidGuard.
> Since the user is apparently called 'squid' you need to,
>
> Either fully login as "squid'' and test this, I advise to test it
> that way *really*.
> If you want to test it from root-originating-shells then,
>
> 1) # su - squid
> 2) squid % _path_to_squidguard/squidGuard
>
>the latter should not give a permission error.
>
>squid.pid contains the process id of the squid process.
>
>Starting as 'squid' using the sudo stuff is bogus, because, indeed,
>then you run into other problems such as the pid file which can not be written,
>e.g. because this file is owned by root.
>
>M.
>
>
>
Sorry, My mistake - again.
[root@localhost mark]# su - squid
This account is currently not available.
hmmm..
[root@localhost mark]# vim /etc/passwd
{change squid:x:23:23::/var/spool/squid:/sbin/nologin to
squid:x:23:23::/var/spool/squid:/bin/bash}
[root@localhost mark]# su - squid
-bash-3.00$ /usr/local/squidguard/bin/squidGuard -d
2006-01-26 20:47:29 [6046] squidGuard 1.2.0 started (1138308449.370)
2006-01-26 20:47:29 [6046] squidGuard ready for requests (1138308449.372)
OK?
Thanks (yet) again...
Mark
Attachment:
signature.asc
Description: OpenPGP digital signature
