Does Linux kernel create a file for a internet domain socket?












3














Linux kernel create a file for a Unix domain socket binded to a pathname.



Does Linux kernel create a file for a internet domain socket? Thanks.






linux socket







share|improve this question






















  • Possible duplicate of Is there a file for each socket?
    – Sergiy Kolodyazhnyy
    4 hours ago
















3














Linux kernel create a file for a Unix domain socket binded to a pathname.



Does Linux kernel create a file for a internet domain socket? Thanks.






linux socket







share|improve this question






















  • Possible duplicate of Is there a file for each socket?
    – Sergiy Kolodyazhnyy
    4 hours ago














3












3








3







Linux kernel create a file for a Unix domain socket binded to a pathname.



Does Linux kernel create a file for a internet domain socket? Thanks.






linux socket







share|improve this question













Linux kernel create a file for a Unix domain socket binded to a pathname.



Does Linux kernel create a file for a internet domain socket? Thanks.






linux socket




linux socket






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked 4 hours ago









Tim

26.2k74246455




26.2k74246455












  • Possible duplicate of Is there a file for each socket?
    – Sergiy Kolodyazhnyy
    4 hours ago


















  • Possible duplicate of Is there a file for each socket?
    – Sergiy Kolodyazhnyy
    4 hours ago
















Possible duplicate of Is there a file for each socket?
– Sergiy Kolodyazhnyy
4 hours ago




Possible duplicate of Is there a file for each socket?
– Sergiy Kolodyazhnyy
4 hours ago










1 Answer
1






active

oldest

votes


















4














No, not in the sense of a file on hard-drive or other block device.



If you look at socket.c in Linux source code, you will see that it creates an inode for sockets, however data is in sockfs filesystem, which is a virtual filesystem within kernel itself, and space is allocated via kmalloc type of function. In that sense, sockets are anonymous files residing in memory.



This brings back to the concept of "everything is a file in Unix", which is a design pattern that focuses on having common utilities to perform same functions similar to files on real physical media. As Linus Torvalds stated:




The whole point with "everything is a file" is not that you have some random filename (indeed, sockets and pipes show that "file" and "filename" have nothing to do with each other), but the fact that you can use common tools to operate on different things.




Thus sockets have inode to have file-like access, but not present on physical filesystem.



However, note, there exist Unix domain sockets, which are IPC type of object intended for process networking, and do reside on disk filesystems.






share|improve this answer

















  • 1




    @Tim I'd say yes. If you look at this they've referenced lsof output: "0xffff8803e256d9c0. That number is actually the address of the relevant in-kernel memory structure or type struct unix_sock". So there has to be an inode in kernel's virtual filesystem corresponding to that
    – Sergiy Kolodyazhnyy
    3 hours ago






  • 1




    And according to Gilles's answer " Unix socket which is not in the filesystem namespace (it can be in the abstract namespace or unnamed)"
    – Sergiy Kolodyazhnyy
    3 hours ago











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f492742%2fdoes-linux-kernel-create-a-file-for-a-internet-domain-socket%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









4














No, not in the sense of a file on hard-drive or other block device.



If you look at socket.c in Linux source code, you will see that it creates an inode for sockets, however data is in sockfs filesystem, which is a virtual filesystem within kernel itself, and space is allocated via kmalloc type of function. In that sense, sockets are anonymous files residing in memory.



This brings back to the concept of "everything is a file in Unix", which is a design pattern that focuses on having common utilities to perform same functions similar to files on real physical media. As Linus Torvalds stated:




The whole point with "everything is a file" is not that you have some random filename (indeed, sockets and pipes show that "file" and "filename" have nothing to do with each other), but the fact that you can use common tools to operate on different things.




Thus sockets have inode to have file-like access, but not present on physical filesystem.



However, note, there exist Unix domain sockets, which are IPC type of object intended for process networking, and do reside on disk filesystems.






share|improve this answer

















  • 1




    @Tim I'd say yes. If you look at this they've referenced lsof output: "0xffff8803e256d9c0. That number is actually the address of the relevant in-kernel memory structure or type struct unix_sock". So there has to be an inode in kernel's virtual filesystem corresponding to that
    – Sergiy Kolodyazhnyy
    3 hours ago






  • 1




    And according to Gilles's answer " Unix socket which is not in the filesystem namespace (it can be in the abstract namespace or unnamed)"
    – Sergiy Kolodyazhnyy
    3 hours ago
















4














No, not in the sense of a file on hard-drive or other block device.



If you look at socket.c in Linux source code, you will see that it creates an inode for sockets, however data is in sockfs filesystem, which is a virtual filesystem within kernel itself, and space is allocated via kmalloc type of function. In that sense, sockets are anonymous files residing in memory.



This brings back to the concept of "everything is a file in Unix", which is a design pattern that focuses on having common utilities to perform same functions similar to files on real physical media. As Linus Torvalds stated:




The whole point with "everything is a file" is not that you have some random filename (indeed, sockets and pipes show that "file" and "filename" have nothing to do with each other), but the fact that you can use common tools to operate on different things.




Thus sockets have inode to have file-like access, but not present on physical filesystem.



However, note, there exist Unix domain sockets, which are IPC type of object intended for process networking, and do reside on disk filesystems.






share|improve this answer

















  • 1




    @Tim I'd say yes. If you look at this they've referenced lsof output: "0xffff8803e256d9c0. That number is actually the address of the relevant in-kernel memory structure or type struct unix_sock". So there has to be an inode in kernel's virtual filesystem corresponding to that
    – Sergiy Kolodyazhnyy
    3 hours ago






  • 1




    And according to Gilles's answer " Unix socket which is not in the filesystem namespace (it can be in the abstract namespace or unnamed)"
    – Sergiy Kolodyazhnyy
    3 hours ago














4












4








4






No, not in the sense of a file on hard-drive or other block device.



If you look at socket.c in Linux source code, you will see that it creates an inode for sockets, however data is in sockfs filesystem, which is a virtual filesystem within kernel itself, and space is allocated via kmalloc type of function. In that sense, sockets are anonymous files residing in memory.



This brings back to the concept of "everything is a file in Unix", which is a design pattern that focuses on having common utilities to perform same functions similar to files on real physical media. As Linus Torvalds stated:




The whole point with "everything is a file" is not that you have some random filename (indeed, sockets and pipes show that "file" and "filename" have nothing to do with each other), but the fact that you can use common tools to operate on different things.




Thus sockets have inode to have file-like access, but not present on physical filesystem.



However, note, there exist Unix domain sockets, which are IPC type of object intended for process networking, and do reside on disk filesystems.






share|improve this answer












No, not in the sense of a file on hard-drive or other block device.



If you look at socket.c in Linux source code, you will see that it creates an inode for sockets, however data is in sockfs filesystem, which is a virtual filesystem within kernel itself, and space is allocated via kmalloc type of function. In that sense, sockets are anonymous files residing in memory.



This brings back to the concept of "everything is a file in Unix", which is a design pattern that focuses on having common utilities to perform same functions similar to files on real physical media. As Linus Torvalds stated:




The whole point with "everything is a file" is not that you have some random filename (indeed, sockets and pipes show that "file" and "filename" have nothing to do with each other), but the fact that you can use common tools to operate on different things.




Thus sockets have inode to have file-like access, but not present on physical filesystem.



However, note, there exist Unix domain sockets, which are IPC type of object intended for process networking, and do reside on disk filesystems.







share|improve this answer












share|improve this answer



share|improve this answer










answered 4 hours ago









Sergiy Kolodyazhnyy

8,35212152




8,35212152








  • 1




    @Tim I'd say yes. If you look at this they've referenced lsof output: "0xffff8803e256d9c0. That number is actually the address of the relevant in-kernel memory structure or type struct unix_sock". So there has to be an inode in kernel's virtual filesystem corresponding to that
    – Sergiy Kolodyazhnyy
    3 hours ago






  • 1




    And according to Gilles's answer " Unix socket which is not in the filesystem namespace (it can be in the abstract namespace or unnamed)"
    – Sergiy Kolodyazhnyy
    3 hours ago














  • 1




    @Tim I'd say yes. If you look at this they've referenced lsof output: "0xffff8803e256d9c0. That number is actually the address of the relevant in-kernel memory structure or type struct unix_sock". So there has to be an inode in kernel's virtual filesystem corresponding to that
    – Sergiy Kolodyazhnyy
    3 hours ago






  • 1




    And according to Gilles's answer " Unix socket which is not in the filesystem namespace (it can be in the abstract namespace or unnamed)"
    – Sergiy Kolodyazhnyy
    3 hours ago








1




1




@Tim I'd say yes. If you look at this they've referenced lsof output: "0xffff8803e256d9c0. That number is actually the address of the relevant in-kernel memory structure or type struct unix_sock". So there has to be an inode in kernel's virtual filesystem corresponding to that
– Sergiy Kolodyazhnyy
3 hours ago




@Tim I'd say yes. If you look at this they've referenced lsof output: "0xffff8803e256d9c0. That number is actually the address of the relevant in-kernel memory structure or type struct unix_sock". So there has to be an inode in kernel's virtual filesystem corresponding to that
– Sergiy Kolodyazhnyy
3 hours ago




1




1




And according to Gilles's answer " Unix socket which is not in the filesystem namespace (it can be in the abstract namespace or unnamed)"
– Sergiy Kolodyazhnyy
3 hours ago




And according to Gilles's answer " Unix socket which is not in the filesystem namespace (it can be in the abstract namespace or unnamed)"
– Sergiy Kolodyazhnyy
3 hours ago


















draft saved

draft discarded




















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • 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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f492742%2fdoes-linux-kernel-create-a-file-for-a-internet-domain-socket%23new-answer', 'question_page');
}
);

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







-

Popular posts from this blog

A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks

Image
0 I found a lot of questions abount appendices and ToC. Many users want appendices to be grouped in an Appendix part, however some problems arise with ToC, hyperref, PDF viewer bookmarks, and so on. There are different solutions which require extra packages, command patching and other extra code, however none of them satisfies me. I almost found an easy way to accomplish a good result, where appendices are added to bookmarks in the right way and hyperref links point to the right page. However, the number of the "Appendix" part page is wrong (it's the number of appendix A). Is there any EASY way to fix that? This is a MWE: documentclass{book} usepackage[nottoc,notlot,notlof]{tocbibind} usepackage{hyperref} begin{document} frontmatter tableofcontents mainmatter part{First} chapter{
Read more

Calculate evaluation metrics using cross_val_predict sklearn

Image
1 In the sklearn.model_selection.cross_val_predict page it is stated: Generate cross-validated estimates for each input data point. It is not appropriate to pass these predictions into an evaluation metric. Can someone explain what does it mean? If this gives estimate of Y (y prediction) for every Y (true Y), why can't I calculate metrics such as RMSE or coefficient of determination using these results? python scikit-learn cross-validation share | improve this question edited Nov 28 '18 at 17:52 desertnaut 20.3k 7 43 79
Read more

Insert data from modal to MySQL (multiple modal on website)

Image
0 I have problem with inserting data to MySQL from modal. My modal: <a href="#" class="badge badge-pill badge-success">6 komentarzy</a> <a href="#" class="badge badge-pill badge-danger">brak komentarzy</a> <a data-toggle="modal" href="#add_desk_comm_{$desk_['desk_id']}" data-target="#add_desk_comm_{$desk_['desk_id']}" class="ediiit">(dodaj)</a> <div class="modal fade" id="add_desk_comm_{$desk_['desk_id']}" tabindex="-1" role="dialog" aria-labelledby="edit_printer" aria-hidden="true"> <div class="modal-dialog" role="document">
Read more