1 |
On Tuesday 25 April 2006 19:41, Duncan wrote: |
2 |
> Nicolas MASSÉ posted <200604251632.37748.nicolas27.masse@×××××××.net>, |
3 |
> |
4 |
> > Don't you think it's a bit strange to have a maximum number of open |
5 |
> > files defined at runtime (ulimit) and another limit (a C constant) |
6 |
> > defined at compilation ? |
7 |
> |
8 |
> No. Some reasonable default limit must be set, and 1024 is a reasonably |
9 |
> sane default. An app can override that default if necessary. For the |
10 |
> vast majority of applications, 1024 files should be plenty. Set the |
11 |
> default higher than that and you are just begging for a buggy application |
12 |
> to DoS the system. It's still possible to do it deliberately with an |
13 |
> override, but in that case it'd have to be a deliberate attack. The |
14 |
> default guards against the unintended. |
15 |
|
16 |
I agree with you that it is necessary to have limits, but I think all limits |
17 |
should be adjustable at runtime or at compile time but not a mix of both ! |
18 |
|
19 |
> > Do you think I should report this as a bug against KTorrent ? KDE ? Qt ? |
20 |
> > libc ? something else ? |
21 |
> |
22 |
> I'd say KTorrent, as that's what's failing to change the normally |
23 |
> reasonable default, for the special case that is KTorrent. If it's simply |
24 |
> using a library there, as is possible, and the override needs to be in the |
25 |
> library, they can bug it upstream or ask you to do so. It's possible, |
26 |
> however, that the 1024 default is a reasonable limit for the library as |
27 |
> well, and ktorrent will need to statically link its own copy, with the |
28 |
> necessary change incorporated. |
29 |
> |
30 |
|
31 |
Ok for Ktorrent, I will see with its team. |
32 |
|
33 |
Thanks for your answer. |
34 |
|
35 |
-- |
36 |
Nicolas MASSÉ |
37 |
Pour récupérer ma clef GPG: |
38 |
gpg --keyserver wwwkeys.eu.pgp.net --recv-keys 0x2A18C433 |
39 |
Key fingerprint: 6621 FC23 5DC7 54BA B952 316A 50B1 BC3F 2A18 C433 |