Bug 103801 - dovecot fails to start under kernel 2.6 with setuid error
Summary: dovecot fails to start under kernel 2.6 with setuid error
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux Beta
Classification: Retired
Component: dovecot   
(Show other bugs)
Version: beta1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact:
URL: dovecot-0.99.10-4
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-09-05 03:08 UTC by Kenneth Topp
Modified: 2007-04-18 16:57 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-09-05 03:20:04 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Kenneth Topp 2003-09-05 03:08:57 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686) Gecko/20030701 Galeon/1.3.7

Description of problem:
Sep  4 22:21:53 static dovecot: Dovecot starting up
Sep  4 22:21:54 static imap-login: setuid(100) failed: Resource temporarily
unavailable
Sep  4 22:21:54 static imap-login: setuid(100) failed: Resource temporarily
unavailable
Sep  4 22:21:54 static dovecot: Login process died too early - shutting down

needs this patch by the author of dovecot.. I assume it's already in upstream
releases:

http://dovecot.procontrol.fi/list/dovecot/2003-July/001945.html

I guess the underlying change in behavior could cause issues in other programs
in moving to 2.6..


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. use 2.6
2. try to start dovecot
    

Actual Results:  doesn't start

Expected Results:  should start

Additional info:

outside of initscripts needing help, this is the only issue I've found with 2.6

Comment 1 Jeremy Katz 2003-09-05 03:20:04 UTC
Fix added for -5


Note You need to log in before you can comment on or make changes to this bug.