On Sun, 2022-01-02 at 17:30 -0500, Wietse Venema wrote:
> Ken Wright:
> > On Sun, 2022-01-02 at 16:01 -0500, Wietse Venema wrote:
> > > Does it also fail when run as root? In that case,
> > >
> > > ??? # strace -e connect postqueue -p |&grep showq
> > >
> > > Otherwise, some temporary hack is needed.
> > >
> > > As root, disdable file permissions:
> > >
> > > # chmod 777 /var/spool/postfix/public
> > > # chmod g-s /usr/sbin/postqueue
> > >
> > > As non-root,list the queue:
> > >
> > > $ strace -e connect postqueue -p
> >
> > Here's the output:
>
> So this is working 'normally'.
>
> Now do the other experiment that temporarily chnages opermissions.
connect(3, {sa_family=AF_UNIX, sun_path="/dev/log"}, 110) = 0
connect(4, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) =
-1 ENOENT (No such file or directory)
connect(4, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) =
-1 ENOENT (No such file or directory)
connect(4, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) =
-1 ENOENT (No such file or directory)
connect(4, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) =
-1 ENOENT (No such file or directory)
connect(4, {sa_family=AF_UNIX, sun_path="public/showq"}, 110) = -1
EACCES (Permission denied)
postqueue: fatal: Connect to the Postfix showq service: Permission
denied
+++ exited with 69 +++
Does this make any sense?
Ken
