Are there any files in /proc which reading them have side effects?
I want to run this command:
grep -r <some pattern> /proc
but since reading files in /proc may result in syscalls، as a precaution I want to be sure that reading (all of) them
does not have any (dangerous) side effects on kernel.
linux grep kernel system-calls
asked Nov 17 '18 at 8:21
gopy
1637
add a comment |
I want to run this command:
grep -r <some pattern> /proc
but since reading files in /proc may result in syscalls، as a precaution I want to be sure that reading (all of) them
does not have any (dangerous) side effects on kernel.
linux grep kernel system-calls
asked Nov 17 '18 at 8:21
gopy
1637
While your question is understandable as it is, the phrase "since reading files in/procmay result in syscalls" is not quite correct. Accessing every file results in syscalls:open(),read()/write(), and so on. This is common for all files, be they regular ones or ones under/proc,/sysand other special filesystems. The difference is a (kernel) code, executing during these syscalls. But you are right in that reading/procfiles involves some specific code execution
– Tsyvarev
Nov 17 '18 at 13:01
add a comment |
I want to run this command:
grep -r <some pattern> /proc
but since reading files in /proc may result in syscalls، as a precaution I want to be sure that reading (all of) them
does not have any (dangerous) side effects on kernel.
linux grep kernel system-calls
asked Nov 17 '18 at 8:21
gopy
1637
I want to run this command:
grep -r <some pattern> /proc
but since reading files in /proc may result in syscalls، as a precaution I want to be sure that reading (all of) them
does not have any (dangerous) side effects on kernel.
linux grep kernel system-calls
linux grep kernel system-calls
asked Nov 17 '18 at 8:21
gopy
1637
asked Nov 17 '18 at 8:21
gopy
1637
asked Nov 17 '18 at 8:21
gopy
1637
asked Nov 17 '18 at 8:21
gopy
1637
asked Nov 17 '18 at 8:21
gopy
1637
1637
While your question is understandable as it is, the phrase "since reading files in/procmay result in syscalls" is not quite correct. Accessing every file results in syscalls:open(),read()/write(), and so on. This is common for all files, be they regular ones or ones under/proc,/sysand other special filesystems. The difference is a (kernel) code, executing during these syscalls. But you are right in that reading/procfiles involves some specific code execution
– Tsyvarev
Nov 17 '18 at 13:01
add a comment |
While your question is understandable as it is, the phrase "since reading files in/procmay result in syscalls" is not quite correct. Accessing every file results in syscalls:open(),read()/write(), and so on. This is common for all files, be they regular ones or ones under/proc,/sysand other special filesystems. The difference is a (kernel) code, executing during these syscalls. But you are right in that reading/procfiles involves some specific code execution
– Tsyvarev
Nov 17 '18 at 13:01
While your question is understandable as it is, the phrase "since reading files in
/proc may result in syscalls" is not quite correct. Accessing every file results in syscalls: open(), read()/write(), and so on. This is common for all files, be they regular ones or ones under /proc, /sys and other special filesystems. The difference is a (kernel) code, executing during these syscalls. But you are right in that reading /proc files involves some specific code execution– Tsyvarev
Nov 17 '18 at 13:01
While your question is understandable as it is, the phrase "since reading files in
/proc may result in syscalls" is not quite correct. Accessing every file results in syscalls: open(), read()/write(), and so on. This is common for all files, be they regular ones or ones under /proc, /sys and other special filesystems. The difference is a (kernel) code, executing during these syscalls. But you are right in that reading /proc files involves some specific code execution– Tsyvarev
Nov 17 '18 at 13:01
add a comment |
1 Answer
1
active
oldest
votes
I have recently read this article about /proc and I think it is very useful and interesting: Making good use of the files in /proc.
As far as I know I can tell you that reading that files wouldn't cause any problem. They represents Linux/Unix statistics and processes.
answered Nov 17 '18 at 8:34
Carlo Federico Vescovo
341113
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53349516%2fare-there-any-files-in-proc-which-reading-them-have-side-effects%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I have recently read this article about /proc and I think it is very useful and interesting: Making good use of the files in /proc.
As far as I know I can tell you that reading that files wouldn't cause any problem. They represents Linux/Unix statistics and processes.
answered Nov 17 '18 at 8:34
Carlo Federico Vescovo
341113
add a comment |
I have recently read this article about /proc and I think it is very useful and interesting: Making good use of the files in /proc.
As far as I know I can tell you that reading that files wouldn't cause any problem. They represents Linux/Unix statistics and processes.
answered Nov 17 '18 at 8:34
Carlo Federico Vescovo
341113
add a comment |
I have recently read this article about /proc and I think it is very useful and interesting: Making good use of the files in /proc.
As far as I know I can tell you that reading that files wouldn't cause any problem. They represents Linux/Unix statistics and processes.
answered Nov 17 '18 at 8:34
Carlo Federico Vescovo
341113
I have recently read this article about /proc and I think it is very useful and interesting: Making good use of the files in /proc.
As far as I know I can tell you that reading that files wouldn't cause any problem. They represents Linux/Unix statistics and processes.
answered Nov 17 '18 at 8:34
Carlo Federico Vescovo
341113
answered Nov 17 '18 at 8:34
Carlo Federico Vescovo
341113
answered Nov 17 '18 at 8:34
Carlo Federico Vescovo
341113
answered Nov 17 '18 at 8:34
Carlo Federico Vescovo
341113
341113
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53349516%2fare-there-any-files-in-proc-which-reading-them-have-side-effects%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
While your question is understandable as it is, the phrase "since reading files in
/procmay result in syscalls" is not quite correct. Accessing every file results in syscalls:open(),read()/write(), and so on. This is common for all files, be they regular ones or ones under/proc,/sysand other special filesystems. The difference is a (kernel) code, executing during these syscalls. But you are right in that reading/procfiles involves some specific code execution– Tsyvarev
Nov 17 '18 at 13:01