> On 2018-03-26, at 21:35, Craig Treleaven <[email protected]> wrote: > > >> On Mar 26, 2018, at 3:17 PM, [email protected] wrote: >> ... >> What do these 2 lines do ? >> --- >> file copy ${portpath}/files/org.macports.munin-cron.plist.in \ >> >> ${destroot}${prefix}/etc/LaunchDaemons/org.macports.munin-cron/org.macports.munin-cron.plist >> >> --- >> >> I have no idea where this "org.macports.munin-cron.plist.in" is supposed to >> be coming from. >> I cannot find it in the original distribution files (didn't assume it would >> be there) nor anywhere ele in macports. >> >> The only "munin-cron.in" in the distribution is >> "./master/_bin/munin-cron.in", and that is the script to run on Linux. >> >> Could somebody please elaborate on startup items ? > > See: > > https://github.com/macports/macports-ports/blob/master/net/munin/files/org.macports.munin-cron.plist.in > > It is supposed to be in the files directory along with the patches. > > MacPorts only supports a single startupitem definition and doesn’t support > periodic execution (every 5 minutes in this case). To get around these > problems, the munin port ships a launchd plist template in the files > directory. The reinplace fixes the path to the executable and then copies it > into the destroot so it will be installed. > > HTH, > > Craig
clear now. thanks! paul.
