Bug 887140
Summary: | New .mount files can't be enabled to boot on startup | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Vasiliy Glazov <vascom2> |
Component: | systemd | Assignee: | systemd-maint |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 17 | CC: | arthur-fayzullin, johannbg, lnykryn, metherid, mschmidt, msekleta, notting, plautrba, systemd-maint, vpavlin |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-05-06 17:49:47 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
Vasiliy Glazov
2012-12-14 06:33:32 UTC
+1 so am I :( (In reply to comment #0) > Steps to Reproduce: > 1. Create new .mount file > 2. Link it to /etc/systemd/system/ Does it work if the unit file is stored directly in the /etc/systemd/system/ directory, rather than merely symlinked there? Yes, it work if the unit file is stored directly in the /etc/systemd/system/ directory. *** This bug has been marked as a duplicate of bug 955379 *** |