Interested to Buy Any Domain ? << Click Here >> for more details...
After the chroot(), calls to socket() are failing. Why?
- 1 Answers
- 2183 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 exactly does SO_KEEPALIVE do?
How many sockets can a port have?
What is the difference between connected and unconnected sockets?
Why do I get EPROTO from read()?
What is the purpose of socket?
How can I tell when a socket is closed on the other end?
How do I convert a string into an internet address?
Why do I get connection refused when the server is not running?
When will my application receive SIGPIPE?
Where is the socket located?
What is with the second parameter in bind()?
What is a socket connection?
Unix Commands 
