After the chroot(), calls to socket() are failing. Why?
- 1 Answers
- 1559 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 a socket api?
Can a socket have multiple ports?
What is socket address with example?
Why does the sockets buffer fill up sooner than expected?
What is a socket address?
What is a sae socket?
What is a socket connection?
Whats the difference between select() and poll()?
Why do we need socket programming?
What is af_inet in socket?
How is a socket created?
What's the difference between a socket and a port?
What are the pros/cons of select(), non-blocking I/O and SIGIO?
What is sae socket?
What is socket address?
