Interested to Buy Any Domain ? << Click Here >> for more details...
After the chroot(), calls to socket() are failing. Why?
- 1 Answers
- 2168 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 |
How can I write a multi-homed server?
How do I send [this] over a socket?
How do unix sockets work?
How many sockets can a cpu have?
What exactly does SO_KEEPALIVE do?
How can I read ICMP errors from connected UDP sockets?
How do I convert a string into an internet address?
How do I use TCP_NODELAY?
What is a socket connection?
Why does the sockets buffer fill up sooner than expected?
How come I get address already in use from bind()?
How can I be sure that UDP messages are received in order?
Unix Commands 
