Re^3: Setting $0 clears /proc/PID/environ too

in reply to Re^2: Setting $0 clears /proc/PID/environ too
in thread Setting $0 clears /proc/PID/environ too

I had to give up using Starman early because of weird issues with internal port allocation (nothing I was doing) and segfaults. I had trouble with it on both OS X and CentOS. I have no idea if it will address your particular deployment issue but I went to uWSGI as my application engine several years ago and it’s been working great with nearly no oversight, on Ubuntu, CentOS, and OS X.

Comment on Re^3: Setting $0 clears /proc/PID/environ too

Replies are listed 'Best First'.
Re^4: Setting $0 clears /proc/PID/environ too by kikuchiyo (Hermit) on Jan 17, 2020 at 22:27 UTC
Thanks for the tip! I was vaguely aware of uWSGI, but I must have dismissed it as a python thing back then. I didn't know it supported Perl out of the box. By the way we don't have too many problems with Starman, it does its job. One grumble I have with it is that it being a descendant of Net::Server::PreFork, it has support for dynamically scaling the number of workers, but this fact is not documented and normally it is set up to use a fixed number of workers.	[reply]

Replies are listed 'Best First'.

Re^4: Setting $0 clears /proc/PID/environ too
by kikuchiyo (Hermit) on Jan 17, 2020 at 22:27 UTC

Thanks for the tip! I was vaguely aware of uWSGI, but I must have dismissed it as a python thing back then. I didn't know it supported Perl out of the box.

By the way we don't have too many problems with Starman, it does its job. One grumble I have with it is that it being a descendant of Net::Server::PreFork, it has support for dynamically scaling the number of workers, but this fact is not documented and normally it is set up to use a fixed number of workers.

[reply]

In Section Seekers of Perl Wisdom