Not a bug. I just followed what Ryan did and everything is working. Thanks.
Here’s the PR: https://github.com/macports/macports-ports/pull/7917
> On Aug 1, 2020, at 9:13 AM, Steven Smith wrote:
>
> I’m trying to update port clam-server to the new syntax, and am hitting the
> following issue.
> Error: Failed to destroot clamav-server: list element in quotes followed by
> ")" instead of space
I’ve tracked this down to the bash line:
> DATE=(/bin/date \"+%FT%T\")"
I am unable to insert any string of this form into the startupitems
init/start/sto
Some ports will need to adjust their usage of
startupitems to be compatible with this change. I believe there are only 4
ports affected, mentioned in that PR, for which I've filed tickets or PRs.
On 2020-6-15 03:04 , Steven Smith wrote:
> Could be a bug. Widespread practice is to code around it and edit the
> launchd .plist’s in the post-activate block.
If there's a bug, report it. It could have been fixed months ago and the
practice wouldn't have needed to become widespread.
- Josh
On Jun 14, 2020, at 11:45, Ryan Schmidt wrote:
> Is this a bug?
On the assumption that it is, I believe this is the fix:
https://github.com/macports/macports-base/pull/191
On Jun 14, 2020, at 12:24, Ryan Schmidt wrote:
> On Jun 14, 2020, at 12:18, Steven Smith wrote:
>
>>> If startupitem support in MacPorts base is not sufficient to express what
>>> we need, it should be enhanced.
>>
>> That’s a good objective. The current st
On Jun 14, 2020, at 12:18, Steven Smith wrote:
>> If startupitem support in MacPorts base is not sufficient to express what we
>> need, it should be enhanced.
>
> That’s a good objective. The current startupitems behavior annoyed me until I
> just learned to copy wh
> If startupitem support in MacPorts base is not sufficient to express what we
> need, it should be enhanced.
That’s a good objective. The current startupitems behavior annoyed me until I
just learned to copy what others had done to code around it.
I’d also note that doing a `man launchd
On Jun 14, 2020, at 12:04, Steven Smith wrote:
> Widespread practice is to code around it and edit the launchd .plist’s in the
> post-activate block. You can use tcl’s reinplace or sh’s plutil as necessary
> to edit the .plists.
>
> Example Portfiles that do this extensively:
>
> •
> https
On 2018-6-4 00:31 , macpo...@parvis.nl wrote:
>
>> On 2018-06-03, at 16:05, Joshua Root wrote:
>>
>> On 2018-6-3 23:53 , macpo...@parvis.nl wrote:
>>> startipitems \
>>> name testit \
>>> executable sudo -u paul /usr/local/bin/testit
>&g
> On 2018-06-03, at 16:05, Joshua Root wrote:
>
> On 2018-6-3 23:53 , macpo...@parvis.nl wrote:
>> startipitems \
>> name testit \
>> executable sudo -u paul /usr/local/bin/testit
>
> Should be:
>
> startupitems \
> name testit \
> e
On 2018-6-3 23:53 , macpo...@parvis.nl wrote:
> startipitems \
> name testit \
> executable sudo -u paul /usr/local/bin/testit
Should be:
startupitems \
name testit \
executable "sudo -u paul /usr/local/bin/testit"
List elements are separated by whitespace, so i
expected result:
ProgramArguments
/opt/port2/bin/daemondo
--label=testit
--start-cmd
sudo
-u
paul
/usr/local/bin/testit
;
--pid=exec
How should I use executable in the new multiple startupitems? or is this a bug
or a feature?
paul.
On 2018-6-1 04:36 , macpo...@parvis.nl wrote:
> - launchd knows when the job died. Why is daemondo even used for an
> executable startupitem?
Unfortunately, launchd also "knows" that a process died when it calls
daemon() or does the equivalent. A lot of daemons do this, and that's
the main reason
Looking through all Portfiles for examples, I found these:
executable sudo -u ${cassandrauser} env \
executable sudo -u elasticsearch ${prefix}/bin/${name}
So I tried this:
startupitem.create yes
startupitems \
name munin-asyncd \
executable sudo -u munin ${prefix}/lib/munin
On 2018-5-30 04:10 , macpo...@parvis.nl wrote:
>
> And how does 'port load ' work with multiple startupitems?
It loads all the startupitems that the port provides.
- Josh
> On 2018-05-27, at 20:41, Joshua Root wrote:
>
> On 2018-5-28 04:14 , macpo...@parvis.nl wrote:
>> I would very much like to us several startupitems for munin's different
>> daemons.
>> However I cannot find any documentation yet, other than patches, and tha
On 2018-5-28 04:14 , macpo...@parvis.nl wrote:
> I would very much like to us several startupitems for munin's different
> daemons.
> However I cannot find any documentation yet, other than patches, and that
> makes it difficult to read and understand.
>
> I created a t
I would very much like to us several startupitems for munin's different
daemons.
However I cannot find any documentation yet, other than patches, and that makes
it difficult to read and understand.
I created a ticket [1] for not being able to compile the github 2.5 guide.
Perhaps one of
On 2018-5-16 05:40 , Rainer Müller wrote:
> It looks like munin-node will fork itself into the background by
> default. This is incompatible with launchd, as it would assume the
> process died as soon as you launch it. Unless there is a switch or
> configuration option to force it to run as a foreg
> On 2018-05-15, at 21:40, Rainer Müller wrote:
>
> On 2018-05-15 20:57, macpo...@parvis.nl wrote:
>>
>>> On 2018-05-15, at 03:56, Ryan Schmidt wrote:
>>>
>>>
>>> On May 14, 2018, at 11:13, macpo...@parvis.nl wrote:
>>>
>&g
On 2018-05-15 20:57, macpo...@parvis.nl wrote:
>
>> On 2018-05-15, at 03:56, Ryan Schmidt wrote:
>>
>>
>> On May 14, 2018, at 11:13, macpo...@parvis.nl wrote:
>>
>>> The Guide states “Executable” StartupItems are preferred over “script”
>>> St
> On 2018-05-15, at 03:56, Ryan Schmidt wrote:
>
>
> On May 14, 2018, at 11:13, macpo...@parvis.nl wrote:
>
>> The Guide states “Executable” StartupItems are preferred over “script”
>> StartupItems.
>>
>> I have 2 daemons that are Perl scri
On 2018-5-15 05:31 , macpo...@parvis.nl wrote:
> Is it possible to create several startupitems for a single port?
>
> Munin always needs a startupitem for munin-node ans uses 'startupitem.create
> yes'.
>
> Next is munin-server, needs to run every 5 minutes, the
On May 14, 2018, at 14:31, macpo...@parvis.nl wrote:
> Is it possible to create several startupitems for a single port?
As of MacPorts 2.5.0, yes. 2.5.0 has not yet been released, but a beta just was.
Is it possible to create several startupitems for a single port?
Munin always needs a startupitem for munin-node ans uses 'startupitem.create
yes'.
Next is munin-server, needs to run every 5 minutes, the current port uses a
plist with StartInterval 300, but that doesn't w
The Guide states “Executable” StartupItems are preferred over “script”
StartupItems.
I have 2 daemons that are Perl scripts, they can run "executable", but the
previous version of the port used a "script".
Any reason not to change that?
> On 2018-03-26, at 21:35, Craig Treleaven wrote:
>
>
>> On Mar 26, 2018, at 3:17 PM, macpo...@parvis.nl wrote:
>> ...
>> What do these 2 lines do ?
>> ---
>>file copy ${portpath}/files/org.macports.munin-cron.plist.in \
>>
>> ${destroot}${prefix}/etc/LaunchDaemons/org.macports.
> On Mar 26, 2018, at 3:17 PM, macpo...@parvis.nl 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
r_local_macports_munin2_net_munin/munin/work/destroot/opt/mpt/etc/LaunchDaemons/org.macports.munin-cron/org.macports.munin-cron.plist":
no such file or directory
Mar 26 20:02:38 Error: Failed to destroot munin: reinplace sed(1) failed
Mar 26 20:02:38 DEBUG: Error code: NONE
Mar 26 20:02:38 D
30 matches
Mail list logo
