https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31074
--- Comment #27 from David Cook <dc...@prosentient.com.au> --- (In reply to Victor Grousset/tuxayo from comment #25) > (In reply to Martin Renvoize from comment #23) > > I had a look to see if there was any obvious way to get the instance name or > > track up to find the parent PID so we could call the HUP call mentioned > > above.. but I failed so far. > > Is a SIGHUP on all starmans running on a large shared hosting server a > paralyzing load? On the occasional plugin install/upgrade/uninstall. If you ran ./misc/devel/install_plugins.pl against all instances, it would be a paralyzing load on a large shared hosting server, yes. If it was just on a web upload or a single install for ./misc/devel/install_plugins.pl then it should be fine since it would just be restarting 1 starman master process. Certainly something to be careful with... I'm a bit apprehensive about giving a web user the ability to restart Starman. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list Koha-bugs@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
