Interested to Buy Any Domain ? << Click Here >> for more details...
After the chroot(), calls to socket() are failing. Why?
- 1 Answers
- 2125 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 do unix sockets work?
What is a deep well socket?
system choose one for me on the connect() call? Should I bind() a port number in my client program, or let the?
How do Sockets Work?
What pieces of information make up a socket?
How would I put my socket in non-blocking mode?
How can I find the full hostname (FQDN) of the system I am running on?
How does a socket work?
Is a socket a file?
Can multiple sockets use the same port?
How is a socket created?
How can I read ICMP errors from connected UDP sockets?
Unix Commands 
