patches/glibc/ports-2.13/650-syslog.patch
| author |
"Yann E. MORIN" <yann.morin.1998@free.fr> |
|
Tue May 08 18:31:10 2012 +0200 (2012-05-08) |
| changeset 2964 |
d48c03998dc1 |
| permissions |
-rw-r--r-- |
scripts: fix catching failures
POSIX 1003.1-2008 does not say whether "set -e" should catch a sub-shell
that exits with !0 (it has a list of conditions to catch, but no list of
conditions not to catch, and this situation is not listed).
bash-3 does not catch such a failure, but bash-4 does. That why, on my
Squeeze system I did not see the issue, while Thomas did on is Lenny chroot.
Reported-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
|
yann@2438
|
1 |
diff -durN glibc-cvs-2.9.orig/misc/syslog.c glibc-cvs-2.9/misc/syslog.c
|
|
yann@2438
|
2 |
--- glibc-cvs-2.9.orig/misc/syslog.c 2009-06-01 10:16:50.000000000 +0200
|
|
yann@2438
|
3 |
+++ glibc-cvs-2.9/misc/syslog.c 2009-06-01 10:17:20.000000000 +0200
|
|
yann@2438
|
4 |
@@ -152,7 +152,7 @@
|
|
yann@2438
|
5 |
#define INTERNALLOG LOG_ERR|LOG_CONS|LOG_PERROR|LOG_PID
|
|
yann@2438
|
6 |
/* Check for invalid bits. */
|
|
yann@2438
|
7 |
if (pri & ~(LOG_PRIMASK|LOG_FACMASK)) {
|
|
yann@2438
|
8 |
- syslog(INTERNALLOG,
|
|
yann@2438
|
9 |
+ __syslog(INTERNALLOG,
|
|
yann@2438
|
10 |
"syslog: unknown facility/priority: %x", pri);
|
|
yann@2438
|
11 |
pri &= LOG_PRIMASK|LOG_FACMASK;
|
|
yann@2438
|
12 |
}
|