[Vm-dev] [OpenSmalltalk/opensmalltalk-vm] Error message for the failure to create heartbeat thread is too specific. (#540)
notifications at github.com
Tue Dec 22 09:50:56 UTC 2020
-----BEGIN PGP SIGNED MESSAGE-----
Well I can understand that Eliot has good reasons to raise the priority
of the heartbeat thread.
Also I have noticed now that I'm running a nice package "AIDA"
(web framework on top of Swazoo) that the WebScheduler is sensitive to
scheduling of course.
My feeling about it is that still the error message is "too specific".
Perhaps the "configure" script could define something like
because I believe the directory /etc/security/limits.d on Linux
is related to a pam_limits package.
The platforms/vm/unix/sqUnixHeartbeat.c could then print the message
Some Linux distros may not even have that directory /etc/security/limits.d.
Regarding Solaris, or other Unix systems that are not Linux, they can have
their own system of privileges to allow/disallow a thread or a process to
set or raise priority.
So although Solaris uses PAM, I could then not define HAVE_LINUX_PAM_LIMITS,
and then at the least the error message would be more suitable.
Although the action to remediate the issue would be different, the
heartbeat thread could still run at a different priority than the main thread.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
-----END PGP SIGNATURE-----
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Vm-dev