Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
This very page says the same: "Note that the value of /proc/sys/kernel/sysrq influences only the invocation via a keyboard. Invocation of any operation via /proc/sysrq-trigger is always allowed (by a user with admin privileges)." Apart from patching the kernel nothing can done.
This very page says the same: "Note that the value of /proc/sys/kernel/sysrq influences only the invocation via a keyboard. Invocation of any operation via /proc/sysrq-trigger is always allowed (by a user with admin privileges)." Apart from patching the kernel nothing can done.
I tried it but when kernel builds the value changes to "y". According guide you can manage it changing CONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE.
There is something wrong in your kernel building process if it changes CONFIG_MAGIC_SYSRQ to "y". It does not do it here, and the new kernel does not have /proc/sysrq-trigger or /proc/sys/kernel/sysrq.
If you compile in the Magic SysRq key support (CONFIG_MAGIC_SYSRQ=y) then you can set the default value of /proc/sys/kernel/sysrq using CONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE.
There is something wrong in your kernel building process if it changes CONFIG_MAGIC_SYSRQ to "y". It does not do it here, and the new kernel does not have /proc/sysrq-trigger or /proc/sys/kernel/sysrq.
If you compile in the Magic SysRq key support (CONFIG_MAGIC_SYSRQ=y) then you can set the default value of /proc/sys/kernel/sysrq using CONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE.
I found why it could not be set "# CONFIG_MAGIC_SYSRQ is not set" because for it you need also disable "# CONFIG_KGDB is not set" only after it you can disable CONFIG_MAGIC_SYSRQ
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.