Many thanks
It fix the issue !
Le 15/09/2021 à 13:08, Graham Wharton a écrit :
You see this when starting as non rootuser. Squid should be started as
root and then it changes identity to cache effective user as defined
in config when it forks.
Graham Wharton
Lube Finder
Tel (UK) : 0800 955 0922
Tel (Intl) : +44 1305 898033
https://www.lubefinder.com
------------------------------------------------------------------------
*From:* squid-users <[email protected]> on
behalf of David Touzeau <[email protected]>
*Sent:* Wednesday, September 15, 2021 11:40:04 AM
*To:* [email protected]
<[email protected]>
*Subject:* [squid-users] squid 5.1/Debian WARNING: no_suid: setuid(0):
(1) Operation not permitted
On Debian 10 64bits with squid 5.1 we have thousand warning as this:
2021/09/15 08:00:18 kid1| WARNING: no_suid: setuid(0): (1) Operation
not permitted
2021/09/15 08:00:18 kid2| WARNING: no_suid: setuid(0): (1) Operation
not permitted
2021/09/15 08:00:18 kid1| WARNING: no_suid: setuid(0): (1) Operation
not permitted
2021/09/15 08:00:18 kid2| WARNING: no_suid: setuid(0): (1) Operation
not permitted
2021/09/15 08:00:18 kid1| WARNING: no_suid: setuid(0): (1) Operation
not permitted
2021/09/15 08:00:18 kid2| WARNING: no_suid: setuid(0): (1) Operation
not permitted
2021/09/15 08:00:18 kid1| WARNING: no_suid: setuid(0): (1) Operation
not permitted
When squid try to load external acls binaries
add chmod 04755 in binaries did not resolve the issue.
No issue with same configuration with squid 3.5x branch
Any tips ?
_______________________________________________
squid-users mailing list
[email protected]
http://lists.squid-cache.org/listinfo/squid-users
