Bug 18365 - reason for different config file handling of autofs?
Summary: reason for different config file handling of autofs?
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: All Linux
Priority: Normal minor
Target Milestone: ---
Assignee: Shlomi Fish
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-05 10:13 CEST by Mike Burgener
Modified: 2016-05-08 13:44 CEST (History)
1 user (show)

See Also:
Source RPM: autofs-5.1.0-4.mga5.x86_64
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Mike Burgener 2016-05-05 10:13:20 CEST 
Hi,

As Setup states, there is a different config-file handling on mageia for autofs.

My question is, is there any good reason for this?
Marja Van Waes 2016-05-08 11:39:44 CEST

CC: (none) => marja11
Assignee: bugsquad => shlomif

Comment 1 Shlomi Fish 2016-05-08 12:21:25 CEST 
Hi Mike,

(In reply to Mike Burgener from comment #0)
> Hi,
> 
> As Setup states, there is a different config-file handling on mageia for
> autofs.
> 
> My question is, is there any good reason for this?

I don't know why this is the case. I just assigned myself as the autofs maintainer.
Comment 2 Marja Van Waes 2016-05-08 13:44:33 CEST 
@ Mike

Please ask your question on dev@ml.mageia.org.

Bug reports are actually meant for bugs and enhancement requests ;-)

Closing this report.

Feel free to reopen it if the answer you get on dev@ml convinces you that there is a bug in our autofs package, or something that needs to be enhanced.

Status: NEW => RESOLVED
Resolution: (none) => INVALID
Note You need to log in before you can comment on or make changes to this bug.