Slim Stop - Slim’s port forwarding is still active even though Slim is stopped

[matthias]

Description

I am also using Herd (PHP) - they are conflicting.
Running them in parallel would be awesome - but for a first step - shutting down slim in a way - that Herd can take over again - would help a lot.

What I found out:
Slim’s port forwarding is still active even though Slim is stopped, so Herd can’t bind to normal web ports.

slim stop

slim doctor && echo '---' && slim list && echo '---' && if [ -f /etc/resolver/test ]; then cat /etc/resolver/test; else echo '/etc/resolver/test missing'; fi && echo '---' && herd --version
Password:
✓  CA certificate         valid, expires 2036-03-10
✓  CA trust               trusted by OS
✓  Port forwarding        active (80→10080, 443→10443)
!  Daemon                 not running
---
No domains or tunnels. Use 'slim start' or 'slim share' to create one.
---
nameserver 127.0.0.1---
Herd 1.26.1

In case I am just doing something wrong - I appreciate the help.

Steps to Reproduce

1. slim stop
2. herd restart

=> not binding

Expected Behavior

Herd can take over after slim stop

Actual Behavior

Slim’s port forwarding is still active even though Slim is stopped, so Herd can’t bind to normal web ports.

Slim Version

0.9.1

Operating System

macOS

Configuration

Logs

slim stop

slim doctor && echo '---' && slim list && echo '---' && if [ -f /etc/resolver/test ]; then cat /etc/resolver/test; else echo '/etc/resolver/test missing'; fi && echo '---' && herd --version
Password:
✓  CA certificate         valid, expires 2036-03-10
✓  CA trust               trusted by OS
✓  Port forwarding        active (80→10080, 443→10443)
!  Daemon                 not running
---
No domains or tunnels. Use 'slim start' or 'slim share' to create one.
---
nameserver 127.0.0.1---
Herd 1.26.1

[qm3ster]

As per #9, this is intentional.
slim is meant for developer machines, not production machines, so nothing should be running on privileged host ports 80 and 443.