Feature #3
problems on parsing "big" files (e.g. c99 shell)
| Status: | Closed | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | Lukas Rist | % Done: | 0% |
|
| Category: | Glastopf | Spent time: | - | |
| Target version: | Next stable release | |||
| Resolution: | wontfix |
Description
the fact that every file is searched for usable variables for output,
and when found, the whole file is "displayed" again til next variable is found,
may lead in timout or broken pipes(?),
means we need a routine to avoid these and for exampe display an error message.
History
Updated by Lukas Rist over 3 years ago
- Status changed from New to Assigned
Updated by Manfred Schilling about 3 years ago
- Status changed from Assigned to Closed
- Resolution set to wontfix
it may have somethingt o do with my console output
i used to see how things are done.
however, we do not need to reply to c99 and such things.
store it and it's done.
i think it's easy to find something that wiould make us able to detect a php shell like r57 c99 or whatever.
i'm closing this ticket now for reopening...