Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 59528
Alias:
Product:
Component:
Status: RESOLVED
Resolution: WONTFIX
Assigned To: Net-Mail Packages <net-mail@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Davin Boling <davin@wordpainter.net>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 59528 depends on: Show dependency tree
Bug 59528 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2004-08-05 08:44 0000 
Attempts to attach the Postfix master process to the strace debugger fail and
leave the master process in a non-working state. One must then individually
kill all Postfix processes before restarting it.

Reproducible: Always
Steps to Reproduce:
1. Start postfix.
2. Determine pid of the "master" process.
3. strace -p masterpid

Actual Results:  
'strace -p 14234' results in the following:
Process 14234 attached - interrupt to quit
trace: ptrace(PTRACE_SYSCALL, ...): Operation not permitted
detach: ptrace(PTRACE_DETACH, ...): Operation not permitted
Process 14234 detached

Expected Results:  
strace should connect to the process and begin to print debugging output to the
screen.

Versions:
mail-mta/postfix-2.0.19
dev-util/strace-4.5.1

------- Comment #1 From Tuan Van (RETIRED) 2004-08-05 09:23:01 0000 ------- 
have you tried to run this as root? I don't have any problem running `strace -p
$(pidof master)`. BTW, I don't have a stable system.
mail-mta/postfix-2.1.3
dev-util/strace-4.5.6

------- Comment #2 From Davin Boling 2004-08-05 09:55:32 0000 ------- 
I was running it as root - but su root. To make sure su wasn't the problem, I
just logged into the terminal directly as root and tried again. Same problem.

This is, for certain, being run as root.

------- Comment #3 From Tim Yamin (RETIRED) 2004-08-05 12:05:56 0000 ------- 
What kernel are you running and are you using any security enhancement patches
such as GRSecurity, SELinux, etc...?

------- Comment #4 From Davin Boling 2004-08-06 10:10:29 0000 ------- 
root # cat /proc/version
Linux version 2.4.20-gentoo-r6 (root@mypostmark.net) (gcc version 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r1, propolice)) #1 SMP Fri Sep 12 12:51:27 EDT 2003

------- Comment #5 From Tim Yamin (RETIRED) 2004-08-06 10:52:16 0000 ------- 
Can you please try gentoo-sources-2.4.26?

------- Comment #6 From Davin Boling 2004-08-10 07:39:57 0000 ------- 
I've confirmed that this problem stems from not having recent enough kernel
sources. All people experiencing this problem should update their kernel
sources to a more recent version.
Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug