Interested to Buy Any Domain ? << Click Here >> for more details...
After the chroot(), calls to socket() are failing. Why?
- 1 Answers
- 2097 Views
- I also Faced
- E-Mail Answers
Answer / chaitanya
On systems where sockets are implemented on top of Streams (e.g. all SysV-based systems, presumably including Solaris), the socket() function will actually be opening certain special files in /dev. You will need to create a /dev directory under your fake root and populate it with the required device nodes (only).
Your system documentation may or may not specify exactly which device nodes are required; suggested checking the man page for ftpd, which should list the files you need to copy and devices you need to create in the chroot'd environment.)
A less-obvious issue with chroot() is if you call syslog(), as many daemons do; syslog() opens (depending on the system) either a UDP socket, a FIFO or a Unix-domain socket. So if you use it after a chroot() call, make sure that you call openlog() *before* the chroot.
| Is This Answer Correct ? | 0 Yes | 0 No |
What is socket address with example?
What is difference between socket and websocket?
What pieces of information make up a socket?
Explain the TIME_WAIT state.
How does unix socket work?
What is Mac, and how is it different from PC? Which one is better for professional users, and why
1 Answers Evolving Systems, IBM,
How to find other end of unix socket connection?
What is with the second parameter in bind()?
What is socket programming in java?
What is the difference between read() and recv()?
How can I find the full hostname (FQDN) of the system I am running on?
How do unix sockets work?
Unix Commands 
