Yes it seems the same bug but the ticket is not relevant (FreeBSD) as
i'm on Debian and on a modern kernel
The main incomprehensible behavior that is issue occurs sometimes as
setuid is a sticky bit permission..
squid -v output:
Squid Cache: Version 4.13
Service Name: squid
This binary
On 14/01/21 3:17 am, David Touzeau wrote:
Hi
This error is generated every 15 minutes when using any authenticator
helper (ntlm, kerberos...)
Is there a way to investigate on this issue ?
kidxx| WARNING: no_suid: setuid(0): (1) Operation not permitted
This looks like
nesday, January 13, 2021 4:17 PM
To: 'Squid Users'
Subject: [squid-users] WARNING: no_suid: setuid(0): (1) Operation not permitted
Hi
This error is generated every 15 minutes when using any authenticator helper
(ntlm, kerberos...)
Is there a way to investigate on this issue ?
kidxx| W
Hi
This error is generated every 15 minutes when using any authenticator
helper (ntlm, kerberos...)
Is there a way to investigate on this issue ?
kidxx| WARNING: no_suid: setuid(0): (1) Operation not permitted
Sometimes, after rebooting the system, issue is fixed for an
undetermined
On 2/6/2013 11:49 PM, Alex Rousskov wrote:
mos, bug 3763 is not about setuid(0) warnings, although both bugs may
have been caused by the same Coverity-inspired motivation to check the
return values of system calls.
Simone, yes, I think you should report the setuid warning bug. If you
do, please
On 02/05/2013 06:08 PM, Amos Jeffries wrote:
On 6/02/2013 3:58 a.m., Simone Levy wrote:
should this issue be reported as a bug or otherwise dealt with?
It is already reported as http://bugs.squid-cache.org/show_bug.cgi?id=3763
Amos, bug 3763 is not about setuid(0) warnings, although both bugs
Hallo there,
should this issue be reported as a bug or otherwise dealt with?
Thanks,
Simone
On 02/04/2013 12:39 pm, Amos Jeffries wrote:
On 4/02/2013 11:35 p.m., Simone Levy wrote:
On 02/01/2013 01:09 AM, Amos Jeffries wrote:
On 1/02/2013 6:03 a.m., Alex Rousskov wrote:
On 01/31/2013 03:06
On 6/02/2013 3:58 a.m., Simone Levy wrote:
Hallo there,
should this issue be reported as a bug or otherwise dealt with?
It is already reported as http://bugs.squid-cache.org/show_bug.cgi?id=3763
The change in 3.2.7 was simply to report several error conditions which
were being silently
On 02/01/2013 01:09 AM, Amos Jeffries wrote:
On 1/02/2013 6:03 a.m., Alex Rousskov wrote:
On 01/31/2013 03:06 AM, Amos Jeffries wrote:
On 31/01/2013 10:24 p.m., Simone Levy wrote:
Hello there,
we are receiving warnings after upgrading squid from version 3.1 to
3.2 on FreeBSD. Squid appears
On 4/02/2013 11:35 p.m., Simone Levy wrote:
On 02/01/2013 01:09 AM, Amos Jeffries wrote:
On 1/02/2013 6:03 a.m., Alex Rousskov wrote:
On 01/31/2013 03:06 AM, Amos Jeffries wrote:
On 31/01/2013 10:24 p.m., Simone Levy wrote:
Hello there,
we are receiving warnings after upgrading squid from
On 02/01/2013 01:09 AM, Amos Jeffries wrote:
Hmm. Yes the warning is new since we started adding debugs() about
failed system calls to display reviously hidden system errors.
Looking at all the documentation about setuid() and seteuid() I'm
wondering if this was supposed to be seteuid(0) -
Hello there,
we are receiving warnings after upgrading squid from version 3.1 to 3.2 on
FreeBSD. Squid appears to be fully operational though.
The warnings seem to be relative to starting the helpers and opening the log
files, but the helpers are started and the log files written to.
# squid
On 31/01/2013 10:24 p.m., Simone Levy wrote:
Hello there,
we are receiving warnings after upgrading squid from version 3.1 to 3.2 on
FreeBSD. Squid appears to be fully operational though.
The warnings seem to be relative to starting the helpers and opening the log
files, but the helpers are
On 01/31/2013 03:06 AM, Amos Jeffries wrote:
On 31/01/2013 10:24 p.m., Simone Levy wrote:
Hello there,
we are receiving warnings after upgrading squid from version 3.1 to
3.2 on FreeBSD. Squid appears to be fully operational though.
The warnings seem to be relative to starting the helpers
On 1/02/2013 6:03 a.m., Alex Rousskov wrote:
On 01/31/2013 03:06 AM, Amos Jeffries wrote:
On 31/01/2013 10:24 p.m., Simone Levy wrote:
Hello there,
we are receiving warnings after upgrading squid from version 3.1 to
3.2 on FreeBSD. Squid appears to be fully operational though.
The warnings
2012/12/12 12:18:28 kid1| Logfile: opening log
daemon:/var/log/squid/access-backend3a.log
2012/12/12 12:18:28 kid1| Logfile Daemon: opening log
/var/log/squid/access-backend3a.log
2012/12/12 12:18:28 kid1| WARNING: no_suid: setuid(0): (1) Operation not
permitted
2012/12/12 12:18:28 kid1|
16 matches
Mail list logo
