/proc/4907/fd/3 -> /usr/local/var/log/openvas/openvasd.messages /proc/4907/fd/4 -> socket:[42319] /proc/4953/fd/5 -> /dev/urandom
And whne I run a scan, in the forked process, I don't see fd/4. ls -l /proc/4939/fd/ 0 1 2 3 5 6 7 8 Chandra. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bernhard Herzog Sent: Wednesday, August 06, 2008 9:23 PM To: [email protected] Subject: Re: [Openvas-devel] [Openvas-commits]r1103-trunk/openvas-libnasl/nasl On 06.08.2008, Chandrashekhar B wrote: > > Also, why can't the socket fd be > > less than 4? I could sort of understand 3 (0, 1, 2 are already taken by > > the standard streams) but 4? Does the openvas server and/or the NASL > > interpreter guarantee that at least one other file is open? > > Yes, the rest of the code seems to just validate for NULL. I always get 4, > let me see if I can do some testing to figure who's eating up 3. According to /proc/<pid>/fd/, on my system fd 3 is /dev/urandom and fd 4 is the nasl script. That's on a Debian Etch GNU/Linux system. Bernhard _______________________________________________ Openvas-devel mailing list [email protected] http://lists.wald.intevation.org/mailman/listinfo/openvas-devel
