After the chroot(), calls to socket() are failing. Why?
- 1 Answers
- 1553 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 come I get address already in use from bind()?
How can I read only one character at a time?
How does unix socket work?
Whats the difference between select() and poll()?
When should I use shutdown()?
How can I put a timeout on connect()?
Why sockets are used?
Are unix sockets faster than tcp?
How come select says there is data, but read returns zero?
system choose one for me on the connect() call? Should I bind() a port number in my client program, or let the?
What's better 6pt or 12pt sockets?
When will my application receive SIGPIPE?
Unix Commands 
