Bug 103448
| Summary: | Bad: configuration file not loaded properly | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Johan Landin <jol> |
| Component: | netatalk | Assignee: | Jason Vas Dias <jvdias> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2005-06-16 22:44:52 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Moved to Fedora Core for investigation against 1.6.4. This bug has been fixed with the latest netatalk-2.0.3-1 release, available from: http://people.redhat.com/~jvdias/netatalk and in tomorrow's rawhide. |
From Bugzilla Helper: User-Agent: Mozilla/4.8 [en] (X11; U; Linux 2.4.20-20.7smp i686) Description of problem: BAD: It is not possible to select the desired user authentication method by setting the desired value(s) in the configuraion file /etc/atalk/afpd.conf. Regardless of what was specified the same default values were always loaded. (uams_clrtxt.so and uams_dhx.so) GOOD: By editing the netatalk startup file /etc/init.d/atalk it was possible to control which UAMs to be loaded. To the line starting afpd (beginning with 'daemon afpd...' ) was added an argument specifiying which configuration file to use: '-F /etc/atalk/afpd.conf' After restarting netatalk using the edited startup script specification of UAMs worked as expected. Version-Release number of selected component (if applicable): netatalk-1.5.2-3 How reproducible: Always Steps to Reproduce: 1. Start netatalk and observe the output in /var/log/messages. 2. Select other values for the uamlist in /etc/atalk/afpd.conf 3. Restart netatalk and observe the output in /var/log/messages regarding which UAMs being loaded. Actual Results: No difference between step 1. and 2. Expected Results: The expected result is to se new values for the UAMs loaded. Additional info: