danielpetri commented on issue #429:
URL:
https://github.com/apache/logging-log4cxx/issues/429#issuecomment-2482083782
@swebb2066 thank you for the investigation. Should I close this ticket? What
is the way of pushing Ubuntu to update to a later, stable release?
--
This is an automated m
swebb2066 commented on issue #429:
URL:
https://github.com/apache/logging-log4cxx/issues/429#issuecomment-2482058861
> Maybe the issue has already been solved on the current master
I can reproduce the problem when using the release version 1.1 code, but not
when using the #431 code
swebb2066 opened a new pull request, #431:
URL: https://github.com/apache/logging-log4cxx/pull/431
This PR fixes a fault accidently introduced in Commit 1a8875a
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL a
swebb2066 opened a new pull request, #430:
URL: https://github.com/apache/logging-log4cxx/pull/430
This PR removes unused parts of build scripts.
As the release review process relies on Github action to package source (to
prevent a XY utils type security problem), the packaging proces
danielpetri commented on issue #429:
URL:
https://github.com/apache/logging-log4cxx/issues/429#issuecomment-2481324403
Yes, sure. This is the query right after I started log4cxxdemo:
```
# ls -l /proc/$(pidof log4cxxdemo)/fd
összesen 0
lrwx-- 1 dpetri dpetri 64 nov 17 16:44
rm5248 commented on issue #429:
URL:
https://github.com/apache/logging-log4cxx/issues/429#issuecomment-2481303611
It seems that current master also has a bug introduced with
https://github.com/apache/logging-log4cxx/commit/1a8875ad839a37d2fcf31876c0bbfe61181c9f21,
which causes the monitor
ppkarwasz merged PR #3174:
URL: https://github.com/apache/logging-log4j2/pull/3174
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubsc
danielpetri opened a new issue, #429:
URL: https://github.com/apache/logging-log4cxx/issues/429
## Description
Log4cxx 1.1.0 (default available on Ubuntu 24.04) does not close file
descriptors when the log server, e.g., chainsaw is not running. Counting number
of sockets remain open.
ppkarwasz commented on issue #3198:
URL:
https://github.com/apache/logging-log4j2/issues/3198#issuecomment-2481034057
> ```
> [ERROR] ===
> [ERROR] Name Type
Delta Ne
danielpetri opened a new issue, #3211:
URL: https://github.com/apache/logging-log4j2/issues/3211
## Description
Log4cxx 1.1.0 (default available on Ubuntu 24.04) does not close file
descriptors when the log server, e.g., chainsaw is not running. The counting
number of sockets remain
danielpetri commented on issue #3211:
URL:
https://github.com/apache/logging-log4j2/issues/3211#issuecomment-2481069946
Moved to log4cxx project.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to
danielpetri closed issue #3211: XMLSocketAppender file descriptors remain open
upon unsuccessful connect
URL: https://github.com/apache/logging-log4j2/issues/3211
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL ab
12 matches
Mail list logo
