You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have smokeping.fcgi started with spawn-fcgi as a service.
It works, but whenever someone requests an incorrect URL, with a section which does not exist, the process terminates, and the website no longer works.
This is because line 1725 in Smokeping.pm explicitly says "die", and spawn-fcgi does not respawn dead processes.
What is the correct way to handle such cases?
Should I add a wrapper over spawn-fcgi to restart the process, or is this an intentional decision to die on errors, in order to encourage the admin to fix the urls?
I.e. if this is a one-off case, I understand it, but giving an anonymous user an opportunity to terminate a service sounds very weird on the first glance.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have smokeping.fcgi started with spawn-fcgi as a service.
It works, but whenever someone requests an incorrect URL, with a section which does not exist, the process terminates, and the website no longer works.
This is because line 1725 in Smokeping.pm explicitly says "die", and spawn-fcgi does not respawn dead processes.
What is the correct way to handle such cases?
Should I add a wrapper over spawn-fcgi to restart the process, or is this an intentional decision to die on errors, in order to encourage the admin to fix the urls?
I.e. if this is a one-off case, I understand it, but giving an anonymous user an opportunity to terminate a service sounds very weird on the first glance.
Beta Was this translation helpful? Give feedback.
All reactions