Bug 1255148
Summary: | init script fails to start | ||
---|---|---|---|
Product: | [Fedora] Fedora EPEL | Reporter: | Sarah Day <sarah.day> |
Component: | znc | Assignee: | Nick Bebout <nb> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | el6 | CC: | nb, silfreed, tsmetana |
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: | 2016-10-07 18:09:53 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
Sarah Day
2015-08-19 18:37:03 UTC
The error message is annoying but it's not the reason znc doesn't start... There is no configuration after the installation and znc fails to start because of it. I made it work by doing the following: 1. Login as root 2. znc -r --makeconf -d /var/lib/znc This will ask many questions and create the configuration in /var/lib/znc When prompted to "Launch ZNC now?", say no. 3. chown -R znc:znc /var/lib/znc ...since we created it as root. 4. service znc start This will spit the error message about extra operand again, but znc seems to start just fine. I understand packaging ZNC is somewhat tough... Maybe fixing the initscript so it would simply refuse to start znc when there is no configuration (and explain why) would make the user's life easier. I am retiring ZNC in epel5 and epel6 since there are deps that are not available. |