Bug 144091

Summary: postfix doesn't start with the latest kernel
Product: [openSUSE] SUSE Linux 10.1 Reporter: Takashi Iwai <tiwai>
Component: BasesystemAssignee: Peter Varkoly <varkoly>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: anders, erik.jacobson, kkaempf, kukuk, sndirsch, susedev
Version: Beta 1   
Target Milestone: ---   
Hardware: Other   
OS: Other   
See Also: http://bugworks.engr.sgi.com/query.cgi/948467
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Fix for postfix-2.2.6 to read the new style proc file
Fixed patch

Description Takashi Iwai 2006-01-19 14:01:48 UTC
postfix doesn't start correctly with the latest kernel (2.6.15-gitx or 2.6.16-rc) because of the change in /proc/net/if_inet6.

A quick fix is below.
Comment 1 Takashi Iwai 2006-01-19 14:03:22 UTC
Created attachment 64011 [details]
Fix for postfix-2.2.6 to read the new style proc file
Comment 2 Takashi Iwai 2006-01-19 14:03:55 UTC
You can find the fixed packages in mbuild bari-tiwai-33.
Comment 3 Takashi Iwai 2006-01-19 14:07:26 UTC
Argh, the patch above isn't good.  Use the one below instead.
Comment 4 Takashi Iwai 2006-01-19 14:08:08 UTC
Created attachment 64013 [details]
Fixed patch
Comment 5 Andreas Schwab 2006-01-19 22:18:49 UTC
*** Bug 144104 has been marked as a duplicate of this bug. ***
Comment 6 Peter Varkoly 2006-01-20 11:20:34 UTC
*** Bug 144303 has been marked as a duplicate of this bug. ***
Comment 7 Andreas Kleen 2006-01-20 22:31:07 UTC
The /proc change has been reverted in mainline, so patching postfix
shouldn't be needed anymore.
Comment 8 Anders Norrbring 2006-01-21 08:13:55 UTC
Doesn't work in beta1 either, the logs say:
Jan 21 09:05:13 luder postfix/postmap[8358]: warning: unexpected data in /proc/net/if_inet6 - skipping IPv6 configuration
Jan 21 09:05:14 luder postfix[8366]: warning: unexpected data in /proc/net/if_inet6 - skipping IPv6 configuration
Comment 9 Olaf Hering 2006-01-22 11:15:42 UTC
.
Comment 10 Martin Lasarsch 2006-01-23 16:16:55 UTC
*** Bug 144831 has been marked as a duplicate of this bug. ***
Comment 11 Martin Lasarsch 2006-01-23 16:18:52 UTC
could somebody please look into it if it's really fixed now or not?