Interested to Buy Any Domain ? << Click Here >> for more details...
After the chroot(), calls to socket() are failing. Why?
- 1 Answers
- 2096 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
How do I convert a string into an internet address?
What is socket programming in java?
How many sockets can a port have?
Is a socket a file?
Is socket a hardware or software?
Can multiple sockets use the same port?
Are unix sockets faster than tcp?
Is tcp or unix socket faster?
Are sockets files?
How do unix sockets work?
What is the difference between read() and recv()?
How does unix socket work?
How can I set the timeout for the connect() system call?
How do I use TCP_NODELAY?
What is the function of socket?
