[MacPorts] #60239: creating startupitem for apache2
MacPorts
noreply at macports.org
Thu Mar 26 16:47:32 UTC 2020
#60239: creating startupitem for apache2
----------------------+--------------------
Reporter: sam452 | Owner: (none)
Type: defect | Status: new
Priority: Low | Milestone:
Component: ports | Version: 2.6.2
Resolution: | Keywords:
Port: apache2 |
----------------------+--------------------
Comment (by ryandesign):
Replying to [comment:3 sam452]:
> sudo port contents apache2 | grep plist
> returns two.
> The expected
> /Library/LaunchDaemons/org.macports.apache2.plist
> which I do not have and
>
/Users/me/macports/etc/LaunchDaemons/org.macports.apache2/org.macports.apache2.plist
> which I had not found until now.
>
> What is odd is that when I viewed the latter file, its contents is not
apache2 but my first attempt to duplicate the working vsftpd plist in
LaunchDaemons/ into a "Save As" into an apache2 plist. I rm'd that attempt
to research if there is an existing plist for my apache2 port.
Sounds like you or something has removed and/or modified files the port
intended to provide. Deactivating and reactivating the port should set
things right again.
> Will deactivating, reactivating the port save my work in the httpd
config files? Thx.
Configuration files will not be overwritten. You can confirm this by
verifying that `port contents apache2` does not mention your .conf files.
(It only mentions .conf.orig files.)
It should be similar for most ports, however it is a manual process to
identify config files and to set it up to do this. If you find a port that
is not set up to preserve your conf files, please file a bug report.
--
Ticket URL: <https://trac.macports.org/ticket/60239#comment:4>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list