Bug 839108
Summary: | autofs-5.0.6-19 fails to start | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Charlie Wyse <charlie.wyse> |
Component: | autofs | Assignee: | Ian Kent <ikent> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 17 | CC: | ikent |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-07-12 01:22:06 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Charlie Wyse
2012-07-11 00:23:45 UTC
(In reply to comment #0) > > Jun 28 11:23:40 lugosi.pdi.com automount[8711]: Starting automounter version > 5.0.6-19.fc17, master map -O retry=10 -DNC1="rwcdtnc...CATION} That's wrong. I have a bug that says that systemd doesn't use ${OPTIONS} properly when OTIONS contains more than a single item. The reporter found that removing the braces made things work again. Can you give that a try please. (In reply to comment #1) > (In reply to comment #0) > > > > Jun 28 11:23:40 lugosi.pdi.com automount[8711]: Starting automounter version > > 5.0.6-19.fc17, master map -O retry=10 -DNC1="rwcdtnc...CATION} > > That's wrong. > I have a bug that says that systemd doesn't use ${OPTIONS} properly > when OTIONS contains more than a single item. The reporter found > that removing the braces made things work again. Can you give that > a try please. That's changing the line: ExecStart=/usr/sbin/automount ${OPTIONS} --pid-file /run/autofs.pid to ExecStart=/usr/sbin/automount $OPTIONS --pid-file /run/autofs.pid in /lib/systemd/system/autofs.service Gave that a shot and it worked. Thanks Ian. Should we just close this as a duplicate of that bug? And I track things via that bug? (In reply to comment #3) > Gave that a shot and it worked. Thanks Ian. Should we just close this as > a duplicate of that bug? And I track things via that bug? I think so. I haven't done anything about it yet because I think maybe it's a systemd bug. I need to poke someone when I get a chance to decide. *** This bug has been marked as a duplicate of bug 836524 *** |