Interested to Buy Any Domain ? << Click Here >> for more details...
After the chroot(), calls to socket() are failing. Why?
- 1 Answers
- 2237 Views
- I also Faced
- E-Mail Answers
Answer Posted / 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 |
Post New Answer View All Answers
What is the function of socket?
What is a sae socket?
What is af_inet in socket?
What's better 6pt or 12pt sockets?
What's the difference between a socket and a port?
Can a socket have multiple ports?
Is there any advantage to handling the signal, rather than just ignoring it and checking for the EPIPE error? Are there any useful parameters passed to the signal catching function?
What is a socket api?
What pieces of information make up a socket?
How can I set the timeout for the connect() system call?
What are the types of sockets?
What is a socket address?
What is difference between socket and websocket?
Why does it take so long to detect that the peer died?
What exactly is a socket?
