Quote:
I can't explain why your attempt to raise your softlimit failed.
Probably I would try to research more on that.
Quote:
The size of the file table is a kernel tunable parameter called nfile.
You need to look at your own kernel to see what that is.
I tried locating it under /dev/kvm but couldn't where should I look for, probably i cannot run System Administration Manager, i dont have root perm.
Quote:
Each file table entry for a file increments a counter in the vnode for that file. If you increment it to far, it would wrap around.
Exactly here is the point, I am trying to exploit the counter for the specific file. Wrapping around - (are the index ptrs to the file table wrapped )
Does that mean mapping a newly created file descriptor to an previously
existing one ? ( I think I am wrong, tht cannot be the case)
Quote:
It may be cheating, but you can have an opened file without opening a file. There are various ways to "dup" a file descriptor. The dup'ed fd points to the same file table entry as the original fd.
I dont agree here, dup function works only on a open file descriptor else it would fail. Though it points to the same file table entry as the original fd, file descriptor entry maintained on a per-process basis would have its available lowest free descriptor entry being used.
Quote:
Unix traditionally limits pid's to 32,000 (but your kernel may have a different limit).
In SunOS, maximum PID no possible is 999, 999 and from sysdef maximum no of processes allowed is 17722
Quote:
So I guess the limit is 32000 * max-fd-per-process.
If that is the case of maximum no of processes possible * 256 ( max-fd-per-process )
literally, I cannot fork that many process to exploit vnode counter for any particular file