Bug#332954: acknowledged by developer (Re: Bug#332954: dash: return from a while condition loses exit status)

2005-11-08 Thread Stephane Chazelas
On Fri, Nov 04, 2005 at 11:36:02AM -0800, Debian Bug Tracking System wrote: [...] It has been closed by one of the developers, namely Gerrit Pape [EMAIL PROTECTED] (reply to [EMAIL PROTECTED]). [...] On Sun, Oct 09, 2005 at 07:55:19PM +0100, Stephane Chazelas wrote: f() { while return

Bug#332954: dash: return from a while condition loses exit status

2005-10-09 Thread Stephane Chazelas
Package: dash Version: 0.5.2-7 Severity: normal f() { while return 2; do :; done } f echo $? The above script outputs 0 while it should output 2. Same goes for: dash -c 'while return 2; do :; done' Same with until instead of while -- System Information: Debian Release: testing/unstable

Bug#397596: posh: $POSH_VERSION contains 0.3.18 for version 0.5

2006-11-08 Thread Stephane Chazelas
Package: posh Version: 0.5 Severity: minor $ env -i posh -c set | grep -i VER POSH_VERSION=0.3.18 BTW, the man page talks about $SH_VERSION, not $POSH_VERSION. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell:

Bug#391918: apache2.2-common: suexec not installed setuid

2006-10-09 Thread Stephane Chazelas
Package: apache2.2-common Version: 2.2.3-1 Severity: important suexec is installed by apache2.2-common as: -rwxr-xr-x 1 root root 10468 2006-10-02 17:19 /usr/lib/apache2/suexec therefore it cannot perform its job, that is change user identities. The suexec man page states that suexec must be

Bug#391393: apache2.2-common: missing modules (/etc/apache2/mods-available vs /usr/lib/apache2/modules vs doc)

2006-10-06 Thread Stephane Chazelas
Package: apache2.2-common Version: 2.2.3-1 Severity: important Hi, Some apache modules that used to be present in apache2-common, and that are referenced in /etc/apache2/mods-available and in apache2.2 documentation are not available anymore. mod_ext_filter is the one I was using, but there

Bug#391393: closed by Tollef Fog Heen [EMAIL PROTECTED] (Bug#391393: fixed in apache2 2.2.3-2)

2006-10-07 Thread Stephane Chazelas
to be installed in the Debian FTP archive: [...] Changes: apache2 (2.2.3-2) unstable; urgency=low . [...] * Stop shipping cern_meta.load, dumpio.load and ext_filter.load. Thanks to Stephane Chazelas for noticing. Closes: #391393 [...] Hi Tollef, thanks, but that's not exactly

Bug#493965: CGI.pm: script_name() include the GET query if it contains //

2008-08-06 Thread Stephane Chazelas
Package: perl-modules Version: 5.10.0-11.1 Severity: normal Tags: patch Note: this bug has already been reported upstreams and I've submitted my patch there as well. http://rt.cpan.org/Public/Bug/Display.html?id=17441 There are a number of issues with the way the CGI.pm constructs script_name()

Bug#493965: CGI.pm: script_name() include the GET query if it contains //

2008-08-07 Thread Stephane Chazelas
FYI, that patch has been applied upstreams and a new version released. CGI.pm 3.40 now fixes it and some other ones. Cheers, Stéphane -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#493965: CGI.pm: script_name() include the GET query if it contains //

2008-08-08 Thread Stephane Chazelas
On Fri, Aug 08, 2008 at 11:33:07AM +0300, Niko Tyni wrote: [...] Thanks. As we now have a separate libcgi-pm-perl package for providing newer versions of CGI.pm, I'm not going to patch the one in perl-modules. The fix will be integrated in the Perl core upstream and get in the Debian perl

Bug#455376: tab completion following mutt -f = no longer works

2007-12-14 Thread Stephane Chazelas
On Fri, Dec 14, 2007 at 01:16:02PM +, Stephane Chazelas wrote: [...] = seems to be transformed at some point to \= and when it reaches _mua_mailboxes, the compset -P '=' fails. Now, we should be able to complete: mutt -f \=... mutt -f '=... so I don't know what the best way to fix

Bug#455376: tab completion following mutt -f = no longer works

2007-12-14 Thread Stephane Chazelas
On Fri, Dec 14, 2007 at 11:03:30AM +, Peter Stephenson wrote: On Thu, 13 Dec 2007 17:12:33 -0500 Paul Kimoto [EMAIL PROTECTED] wrote: unsetopt equals autoload -U compinit compinit zstyle ':completion:*' mail-directory $HOME/email zstyle ':completion:*:warnings' format 'No

Bug#451361: pax: -s option with or \1, \2... doesn't work

2007-11-15 Thread Stephane Chazelas
Package: pax Version: 1:1.5-15 Severity: important Tags: patch Hi ya $ touch foobar $ echo foobar | pax -rwds '/.*//P' . pax: Replacement name error foobar This is because the resub() function that does the replacement, upon a '', attempts to copy data from the _pattern_ string (above: .*)

Bug#454414: zsh-beta: missing terminfo module

2007-12-05 Thread Stephane Chazelas
Package: zsh-beta Version: 4.3.4-dev-3+20071203-1 Severity: important $ zmodload zsh/terminfo zsh: failed to load module `zsh/terminfo': /usr/lib/zsh-beta/4.3.4-dev-3/zsh/terminfo.so: cannot open shared object file: No such file or directory Even though it was there in previous versions and

Bug#436438: kill -s num is not POSIX but understood as kill -num by posh

2007-08-07 Thread Stephane Chazelas
Package: posh Version: 0.5.5 Severity: minor As per http://www.opengroup.org/onlinepubs/009695399/utilities/kill.html, the syntax for kill is SYNOPSIS 1 kill -s signal_name pid ... 2 kill -l [exit_status] 3 ^[XSI] [Option Start] kill [-signal_name] pid ... 4 kill [-signal_number] pid

Bug#436438: kill -s num is not POSIX but understood as kill -num by posh

2007-08-07 Thread Stephane Chazelas
On Tue, Aug 07, 2007 at 09:32:58AM -0400, Clint Adams wrote: On Tue, Aug 07, 2007 at 02:21:55PM +0100, Stephane Chazelas wrote: But if posh was really pedantic, it should not accept kill -s signal_number pid. Agreed: it should accept only names and 0. Hi Clint, I'm glad we agree

Bug#31464: regexp search in info

2007-09-18 Thread Stephane Chazelas
On Mon, Sep 17, 2007 at 09:42:53PM +0200, Frank Küster wrote: Stephane Chazelas [EMAIL PROTECTED] wrote: As I can see debian doesn't seem to sync up anymore with gnu on this one, Uups, how do you come to that conclusion? We don't have 4.9 yet (but most of the patches for 4.8a should

Bug#446917: mimedecode: attached rfc822 emails stop the processing of an email

2007-10-16 Thread Stephane Chazelas
Package: mimedecode Version: 1.9-4 Severity: important Please consider this email as input (a stripped-down email with 2 email attachments): | MIME-Version: 1.0 | Content-Type: multipart/mixed; | boundary=_=_NextPart_026_01C81003.683F8A00 | | --_=_NextPart_026_01C81003.683F8A00 |

Bug#446922: mimedecode: in nested parts, the outer content-transfer-encoding should be changed from 7bit to 8 bit when applicable

2007-10-16 Thread Stephane Chazelas
Package: mimedecode Version: 1.9-4 Severity: normal Please consider this input email: | MIME-Version: 1.0 | Content-Type: multipart/mixed; | boundary=_=_NextPart_026_01C81003.683F8A00 | | --_=_NextPart_026_01C81003.683F8A00 | Content-Type: message/rfc822 |

Bug#429021: builtin echo command redirection misbehaves in detached scripts when terminal is closed

2007-09-09 Thread Stephane Chazelas
On Sun, Sep 09, 2007 at 10:08:14PM +0200, Andreas Schwab wrote: Stephane Chazelas [EMAIL PROTECTED] writes: On Sun, Sep 09, 2007 at 07:10:59PM +0100, Stephane Chazelas wrote: [...] What OS and version of glibc? I do get the error message but I get both a and b in the file

Bug#429021: builtin echo command redirection misbehaves in detached scripts when terminal is closed

2007-09-10 Thread Stephane Chazelas
On Mon, Sep 10, 2007 at 12:05:57AM +0200, Aurelien Jarno wrote: [...] bash -c 'echo a; echo b a' - is enough for me to reproduce the problem. [both a and b seen in file a.] Guess you have a buggy libc, then. [...] I wouldn't be surprised if it has to do with the fix to debian

Bug#429021: builtin echo command redirection misbehaves in detached scripts when terminal is closed

2007-09-10 Thread Stephane Chazelas
On Mon, Sep 10, 2007 at 11:56:33AM +0400, Dmitry Potapov wrote: On Sun, Sep 09, 2007 at 10:18:07PM +0100, Stephane Chazelas wrote: Now, I'm not sure if we can say that the new glibc behavior observed is bogus (other than it's different from the behavior observed in all the libcs I tried

Bug#429021: builtin echo command redirection misbehaves in detached scripts when terminal is closed

2007-09-10 Thread Stephane Chazelas
On Mon, Sep 10, 2007 at 02:17:41PM +0400, Dmitry Potapov wrote: [...] On Mon, Sep 10, 2007 at 09:08:33AM +0100, Stephane Chazelas wrote: thanks for replying, I gave a list in another email. I tried on Solaris 7 and HPUX and both seem to flush the buffer upon an unsuccessful fflush() I

Bug#429021: builtin echo command redirection misbehaves in detached scripts when terminal is closed

2007-09-10 Thread Stephane Chazelas
On Mon, Sep 10, 2007 at 11:57:34AM -0400, Chet Ramey wrote: Andreas Schwab wrote: Chet Ramey [EMAIL PROTECTED] writes: What's needed is a portable interface like BSD's fpurge(3). This is also available from glibc as __fpurge (likewise on Solaris). Yes, though I have an aversion to

Bug#429021: builtin echo command redirection misbehaves in detached scripts when terminal is closed

2007-09-10 Thread Stephane Chazelas
On Mon, Sep 10, 2007 at 09:25:26PM +0400, Dmitry Potapov wrote: [...] With dietlibc: $ ./t signal handler called, sig=2 writer: num_bytes=80008 num_lines=10001 writer: expected num_bytes=8 but was 80008 reader: num_bytes=80007 num_lines=1 reader: number of missing bytes:

Bug#31464: regexp search in info

2007-09-16 Thread Stephane Chazelas
Hi guys, just to let you know that I've submitted a patch that addresses that at savannah.org: https://savannah.gnu.org/bugs/?15572 There's another one for the other limitation that used to bother me in info: the fact that the index doesn't take you where it should:

Bug#442858: libc6-prof: programs linked agains libc_p.a crash with a SEGV

2007-09-17 Thread Stephane Chazelas
Package: libc6-prof Version: 2.6.1-4 Severity: grave Justification: renders package unusable Hi, I don't seem to able build any program linked against the profiled version of the glibc. I can reproduce the problem with any version of gcc (3.3, 3.4, 4.0, 4.1, 4.2), with 2.6.1-1 and 2.6.1-4.

Bug#483860: posh: local can't be used as a function name

2008-05-31 Thread Stephane Chazelas
Package: posh Version: 0.6.7 Severity: normal $ local() { echo a; } $ local a $ local a $ local is not a POSIX command, but I suspect it might be a debian policy extension to POSIX which may explain why posh has it. Anyway, the above breaks POSIX conformance I think. POSIX only allows select

Bug#483860: posh: local can't be used as a function name

2008-06-01 Thread Stephane Chazelas
On Sun, Jun 01, 2008 at 02:26:37AM +, Clint Adams wrote: On Sat, May 31, 2008 at 06:21:35PM +0100, Stephane Chazelas wrote: $ local() { echo a; } $ local a $ local a $ [...] Anyway, the above breaks POSIX conformance I think. POSIX only allows select and function as possible non

Bug#483860: posh: local can't be used as a function name

2008-06-02 Thread Stephane Chazelas
On Sun, Jun 01, 2008 at 01:15:24PM +, Clint Adams wrote: On Sun, Jun 01, 2008 at 12:11:39PM +0100, Stephane Chazelas wrote: then, posh has another problem with the other special builtins. As far, as I can tell, POSIX doesn't say that special builtin names can't be used as functions

Bug#483860: posh: local can't be used as a function name

2008-06-02 Thread Stephane Chazelas
On Mon, Jun 02, 2008 at 03:04:55PM +, Clint Adams wrote: On Mon, Jun 02, 2008 at 11:58:59AM +0100, Stephane Chazelas wrote: Another strange requirement that I see no shell implements even posh, is that if a builtin (such as [ or echo or :) is not found in $PATH, its invocation should

Bug#470886: xserver-xorg-input-kbd: repeated KeyPress events when switching VT while pressing a key

2008-06-04 Thread Stephane Chazelas
On Sun, Mar 16, 2008 at 04:21:50PM +0100, Brice Goglin wrote: [...] If, from xorg, I switch to another VT while pressing a key, the original X server keeps sending keypress events to the previously focused client (and keyrelease events to some other client which I've not determined) at the

Bug#481334: nagios3 package upgrade leaves nagios3 stopped.

2008-05-15 Thread Stephane Chazelas
Package: nagios3 Version: 3.0.1-1 Severity: important Hiya, I can see nagios3 is stopped in nagios3-common and nagios3 installation scripts but started only in nagios3-common. So if one upgrades only nagios3, nagios is stopped but not started after the installation. $ grep -r 'nagios3 st'

Bug#484936: posh: problem in error message upon incorrect substitution

2008-06-07 Thread Stephane Chazelas
Package: posh Version: 0.6.7 Severity: minor $ posh -c 'echo ${=}' posh: : bad substitution Same for all sorts of incorrect substitutions. The bug is inherited from pdksh it seems. It also seems to have been fixed in mksh. $ pdksh -c 'echo ${=}' pdksh: : bad substitution $ mksh -c 'echo ${=}'

Bug#334182: dash's a=x b=$a problem

2008-06-09 Thread Stephane Chazelas
Hi, I was about to submit another bug report about that (the fact that a=x b=$a; echo $b doesn't output x) when I saw there was one already. I was surprised to see: Tags: wontfix; I read through the lengthy discussion, but it doesn't explain why it's tagged as wontfix. Both common sense and

Bug#334182: dash's a=x b=$a problem

2008-06-09 Thread Stephane Chazelas
On Mon, Jun 09, 2008 at 03:36:29PM +0100, Stephane Chazelas wrote: [...] I was about to submit another bug report about that (the fact that a=x b=$a; echo $b doesn't output x) when I saw there was one already. I was surprised to see: Tags: wontfix; I read through the lengthy

Bug#485463: posh: calling a function with var=value func

2008-06-09 Thread Stephane Chazelas
Package: posh Version: 0.6.7 Severity: normal $ f() { echo $a; } $ a=1 f 1 $ echo $a 1 If I read SUSv3 correctly, the echo statement shouldn't have output 1. Now it's true that in cases like: $ ksh93 -c 'f() { a=2; }; a=1 f; echo $a' 2 $ bash -c 'f() { a=2; }; a=1 f; echo $a' $ pdksh -c

Bug#483860: posh: local can't be used as a function name

2008-06-10 Thread Stephane Chazelas
On Mon, Jun 02, 2008 at 05:12:45PM +0100, Stephane Chazelas wrote: On Mon, Jun 02, 2008 at 03:04:55PM +, Clint Adams wrote: On Mon, Jun 02, 2008 at 11:58:59AM +0100, Stephane Chazelas wrote: Another strange requirement that I see no shell implements even posh, is that if a builtin

Bug#485607: posh: Using [ (aka test) unquoted causes globbing to be performed

2008-06-10 Thread Stephane Chazelas
Package: posh Version: 0.6.7 Severity: normal Doing: [ a = a ] causes posh to read the content of the current directory which slows scripts down significantly if the current directory is big. set -f; [ a = a ] or \[ a = a ] stops posh from doing that which suggests globbing is involved.

Bug#485636: manpages-dev: nanosleep(2) and high resolution timers

2008-06-10 Thread Stephane Chazelas
Package: manpages-dev Version: 2.79-4 Severity: wishlist The BUGS section in nanosleep(2) gives: BUGS The current implementation of nanosleep() is based on the normal kernel timer mechanism, which has a resolution of 1/HZ s (see time(7)). Therefore, nanosleep() pauses

Bug#485607: posh: Using [ (aka test) unquoted causes globbing to be performed

2008-06-10 Thread Stephane Chazelas
On Tue, Jun 10, 2008 at 12:28:27PM +0100, Stephane Chazelas wrote: Package: posh Version: 0.6.7 Severity: normal Doing: [ a = a ] causes posh to read the content of the current directory which slows scripts down significantly if the current directory is big. set -f

Bug#485636: manpages-dev: nanosleep(2) and high resolution timers

2008-06-11 Thread Stephane Chazelas
On Wed, Jun 11, 2008 at 08:52:24AM +0200, Michael Kerrisk wrote: [...] I think it should be worth mentionning that since 2.6.16, on some architectures, the kernel can be configured with high resolution timers which makes nanosleep(2) a lot more accurate and voids the first comment above.

Bug#485809: bsdmainutils: [columns] -n option not documented as a debian extension

2008-06-11 Thread Stephane Chazelas
Package: bsdmainutils Version: 6.1.10 Severity: minor Hiya, The -n option seems to be a debian only extension added to fix http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=183877 The man page suggests that it is the column from 4.3BSD-Reno as found on all BSDs and most Linux for decades. So

Bug#334182: dash's a=x b=$a problem

2008-06-12 Thread Stephane Chazelas
On Wed, Jun 11, 2008 at 08:09:13PM -0500, Raphael Geissert wrote: Stephane Chazelas wrote: .. 3$ b=x f x 4$ echo $b x and (4) shouldn't have output x if I read POSIX correctly. This is a known issue of some shells. http://code.dogmap.org/lintsh/ : var=value command

Bug#478019: zsh: Should handle non-breaking space as word separator

2008-04-26 Thread Stephane Chazelas
On Sat, Apr 26, 2008 at 04:05:48PM +0100, Clint Adams wrote: On Sat, Apr 26, 2008 at 12:00:03PM +0100, Samuel Thibault wrote: Hello, On a french keyboard, '|' is typed by using alt-gr, and the non-breaking space is often typed by using alt-gr space. That often leads to this: € echo

Bug#478850: posh: $ENV variable processed by non-interactive shells

2008-05-01 Thread Stephane Chazelas
Package: posh Version: 0.6.6 Severity: normal Hiya, $ echo echo in a $ ENV=./a posh -c : in $ ENV=./a posh ./a in in According to SUSv3: ENV ^[UP XSI] [Option Start] The processing of the ENV shell variable shall be supported on all XSI-conformant systems

Bug#478850: posh: $ENV variable processed by non-interactive shells

2008-05-01 Thread Stephane Chazelas
2008-05-01 14:05:11 +0100, Clint Adams: On Thu, May 01, 2008 at 01:47:46PM +0100, Stephane Chazelas wrote: So, first it's an XSI extension, so I guess posh is not required to implement it, but as it does, I think it shouldn't read the $ENV file when not interactive. Hmm, it's probably

Bug#478850: posh: $ENV variable processed by non-interactive shells

2008-05-01 Thread Stephane Chazelas
2008-05-01 14:47:54 +0100, Clint Adams: On Thu, May 01, 2008 at 02:33:04PM +0100, Stephane Chazelas wrote: I don't really care about the interactive side of things ($ENV, $PSx, job control), but I tend to consider that for the scripting side of things, the optional features should

Bug#478871: lsb-base: killproc stops a process if a signal number is provided

2008-05-01 Thread Stephane Chazelas
Package: lsb-base Version: 3.2-11 Severity: important In /lib/lsb/init-functions, we read: killproc () { [...] sig=$(echo ${2:-} | sed -e 's/^-\(.*\)/\1/') sig=$(echo $sig | sed -e 's/^SIG\(.*\)/\1/') if [ -n $sig -o $sig = 15 -o $sig = TERM ]; then is_term_sig=yes fi

Bug#478877: hardcoded /usr/local/nagios/var in /usr/lib/nagios3/p1.pl (for debug) should be updated ideally

2008-05-01 Thread Stephane Chazelas
Package: nagios3 Version: 3.0.1-1 Severity: minor Hiya, Everything is in the subject. This is only for debug purposes and that file has to be edited anyway to turn debug on, so this is very minor, but that file has: use constantDEBUG_LOG_PATH = '/usr/local/nagios/var/' ; It would

Bug#478889: permissions for /var/lib/nagios3/rw/nagios.cmd incorrect

2008-05-01 Thread Stephane Chazelas
Package: nagios3 Version: 3.0.1-1 Severity: normal Hiya, $ sudo ls -ld /var/lib/nagios3{,/rw{,/nagios.cmd}} drwxr-x--- 5 nagios nagios 4096 2008-04-30 14:46 /var/lib/nagios3 drwx-- 2 nagios www-data 4096 2008-05-01 16:43 /var/lib/nagios3/rw prw-rw 1 nagios nagios 0 2008-05-01

Bug#478906: nagios-plugins: perl plugins failure when run by embedded perl interpreter

2008-05-01 Thread Stephane Chazelas
Package: nagios-plugins Version: 1.4.11-2 Severity: normal When perl plugin scripts are run with the embedded perl interpreter in nagios3, the shift perl command doesn't shift @ARGV, but @_ (which happens to contain the same thing as @ARGV at the time the script was started). So, if we take the

Bug#478889: [Pkg-nagios-devel] Bug#478889: permissions for /var/lib/nagios3/rw/nagios.cmd incorrect

2008-05-01 Thread Stephane Chazelas
2008-05-01 18:28:34 +0200, Alexander Wirt: tag 478889 wontfix thanks [...] Please read README.Debian. [...] Alright, sorry about that. regards, Stephane -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#479013: check_dig: no check for mandatory parameter -l

2008-05-02 Thread Stephane Chazelas
Package: nagios-plugins Version: 1.4.11-2 Severity: minor Hiya, $ ./check_dig -h check_dig v1590 (nagios-plugins 1.4.11) [...] Usage:check_dig -H host -l lookup [-p server port] [-T query type] [-w warning interval] [-c critical interval] [-t timeout] [-a expected answer address] [-v] -l

Bug#476519: [Pkg-shadow-devel] Bug#476519: shell-mode garbles input

2008-05-02 Thread Stephane Chazelas
On Fri, May 02, 2008 at 06:08:41AM +0800, [EMAIL PROTECTED] wrote: As http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=476519 says, maybe it is a bash bug: with Debian sid's BASH_VERSION=3.2.33(1)-release about half the time the below works normally, the other half some magic hand sends exit

Bug#479044: nagios3: incorrect error message for duplicate service on host

2008-05-02 Thread Stephane Chazelas
Package: nagios3 Version: 3.0.1-1 Severity: minor When a service for a given host is duplicated, one gets this kind of error message: Duplicate definition found for service 'localhost' on host 'DNS: spider.com' (config file '/etc/nagios3/conf.d/ant.cfg', starting on line 111) There's obviously

Bug#479045: nagios-plugins: check_disk wrongly treats devices as being NFS shares

2008-05-02 Thread Stephane Chazelas
Package: nagios-plugins Version: 1.4.11-2 Severity: normal Hiya, check_disk -l or -L is meant to check only the local file systems, so it excludes the NFS mounted ones. But to do so, it checks whether the mount device contains a : instead of checking the filesystem type. For instance, that

Bug#479051: nagios3: wrong home directory for the nagios user

2008-05-02 Thread Stephane Chazelas
Package: nagios3 Version: 3.0.1-1 Severity: normal The nagios user is being added by /usr/sbin/useradd -r -d /var/log/nagios -s /bin/sh -c %{nsusr} %{nsusr} However, the /var/log/nagios doesn't exist in nagios3, it's /var/log/nagios3. It can be a problem when wanting to add a check for the rsh

Bug#479051: Acknowledgement (nagios3: wrong home directory for the nagios user)

2008-05-02 Thread Stephane Chazelas
The argument about rsh is not so good given that the shell is /bin/false so rsh wouldn't work anyway. Cheers, Stephane -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#479061: nagios3: dereference NULL pointer when a check command returns no output

2008-05-02 Thread Stephane Chazelas
Package: nagios3 Version: 3.0.1-1 Severity: normal If a check command returns no output at all, you see the output being (null) with the glibc and you would get a SEGV with other libc's. This is because of: checks.c 2975 /* initialize dynamic buffer for storing plugin output */ 2976

Bug#476519: [Pkg-shadow-devel] Bug#476519: shell-mode garbles input

2008-05-02 Thread Stephane Chazelas
On Fri, May 02, 2008 at 11:27:00PM +0800, [EMAIL PROTECTED] wrote: SC Try SC sudo env -i SHELLOPTS=xtrace su -p - nobody (I don't use sudo) uid=0(root) gid=0(root) groups=0(root) # env -i SHELLOPTS=xtrace su -p - nobody + PATH=/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games + '['

Bug#476519: [Pkg-shadow-devel] Bug#476519: shell-mode garbles input

2008-05-02 Thread Stephane Chazelas
On Fri, May 02, 2008 at 11:27:00PM +0800, [EMAIL PROTECTED] wrote: SC Try SC sudo env -i SHELLOPTS=xtrace su -p - nobody (I don't use sudo) uid=0(root) gid=0(root) groups=0(root) # env -i SHELLOPTS=xtrace su -p - nobody + PATH=/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games + '['

Bug#476519: [Pkg-shadow-devel] Bug#476519: shell-mode garbles input

2008-05-02 Thread Stephane Chazelas
On Sat, May 03, 2008 at 12:30:02AM +0800, [EMAIL PROTECTED] wrote: Here we see the typical deal. You asked me about ulimit. [..] Could you try ulimit -a? Have you got a lot of processes running as nobody? $ ps -fjlLunobody $ sudo lsof -u nobody Or maybe it could be su that exits and bash

Bug#482389: route.8.gz: incorrect description for irtt

2008-05-22 Thread Stephane Chazelas
Package: net-tools Version: 1.60-19 Severity: minor route(8) says: irtt I set the initial round trip time (irtt) for TCP connections over this route to I milliseconds (1-12000). This is typically only used on AX.25 networks. If omitted the RFC 1122 default of 300ms is used. RFC

Bug#482346: zsh doesn't always wait for its children (- zombie)

2008-05-24 Thread Stephane Chazelas
On Sat, May 24, 2008 at 03:25:04PM +0100, Peter Stephenson wrote: On Sat, 24 May 2008 14:44:45 +0200 Vincent Lefevre [EMAIL PROTECTED] wrote: This is 100% reproducible with both zsh and zsh-beta. If it's just a matter of starting vlc and trying to kill it for you, then there's something

Bug#482346: zsh doesn't always wait for its children (- zombie)

2008-05-24 Thread Stephane Chazelas
On Sat, May 24, 2008 at 04:27:04PM +0100, Stephane Chazelas wrote: [...] Note that both mksh and posh are meant to derive from pdksh. It would be interesting to know why posh switched from sigsuspend to wait4. [...] I'm under the impression that it is by accident/mistake, the conf-end.h

Bug#482346: zsh doesn't always wait for its children (- zombie)

2008-05-24 Thread Stephane Chazelas
On Sat, May 24, 2008 at 10:41:07AM -0700, Bart Schaefer wrote: [...] But if *that* were a tight loop, it would mean that signal_suspend() isn't working. It'd be nice to know what process or processes send the load so high; 100% CPU usage is one thing, but 26+ processes in runnable state

Bug#482346: zsh doesn't always wait for its children (- zombie)

2008-05-25 Thread Stephane Chazelas
On Sun, May 25, 2008 at 02:41:01AM +0200, Vincent Lefevre wrote: On 2008-05-24 16:40:02 -0700, Phil Pennock wrote: Since you're on a rarer architecture that doesn't see so much Linux kernel debugging, I'd be inclined to look at what has changed in the kernel's architecture-specific signal

Bug#480371: ash: export -p may output incorrect variables

2008-06-29 Thread Stephane Chazelas
On Thu, Jun 12, 2008 at 04:24:58PM +, Gerrit Pape wrote: On Fri, May 09, 2008 at 04:34:14PM +0100, Stephane Chazelas wrote: ~$ env -i '1=' ash -c 'export' export 1='' export PWD='/home/chazelas' $ env -i '=' ash -c 'export' export ='' export PWD='/home/chazelas' ash should

Bug#478942: [Pkg-nagios-devel] Bug#478942: nagios-plugins: check_disk_smb and no-user or no-passwd or share with spaces...

2008-07-03 Thread Stephane Chazelas
On Wed, Jul 02, 2008 at 04:04:48PM +0200, Jan Wagner wrote: Hi Stephane I got a bugreport about check_disk_smb (#488820). Maybe this line was removed accidently: On Thursday 01 May 2008 22:34, Stephane Chazelas wrote: -my $smbclientoptions= $opt_P ? -p $opt_P : ; Thanks

Bug#478942: closed by Jan Wagner [EMAIL PROTECTED] (Bug#478942: fixed in nagios-plugins 1.4.12-1)

2008-06-19 Thread Stephane Chazelas
usage of smbclient, thanks Stephane Chazelas [EMAIL PROTECTED] for providing it and adding ' around arguments in plugin configs (Closes: #478942) [...] Hi Jan, there seems to have been a problem with that patch. The patch file itself adds a .rej file. Attached is the output

Bug#487254: manpages-dev: *scanf may set errno to ERANGE

2008-06-20 Thread Stephane Chazelas
Package: manpages-dev Version: 2.80-1 Severity: normal In the GNU and UC versions of the libc (at least), the scanf/fscanf/sscanf... functions seem to be calling strtoxxx internally for number conversions. In doing so, errno may be set to ERANGE when the input doesn't fit in the number size

Bug#487254: manpages-dev: *scanf may set errno to ERANGE

2008-06-20 Thread Stephane Chazelas
On Fri, Jun 20, 2008 at 04:35:27PM +0100, Stephane Chazelas wrote: [...] In the GNU and UC versions of the libc (at least), the scanf/fscanf/sscanf... functions seem to be calling strtoxxx internally for number conversions. In doing so, errno may be set to ERANGE when the input doesn't fit

Bug#487254: manpages-dev: *scanf may set errno to ERANGE

2008-06-23 Thread Stephane Chazelas
On Mon, Jun 23, 2008 at 10:34:14AM +0200, Michael Kerrisk wrote: [...] Okay -- I verified this. One of the problems here of course is that the scanf.3 page currently doesn't document *any* errors... and possibly to EINVAL for a figures not in the requested base. Can you provide an

Bug#487254: manpages-dev: *scanf may set errno to ERANGE

2008-06-23 Thread Stephane Chazelas
On Mon, Jun 23, 2008 at 11:08:45AM +0200, Michael Kerrisk wrote: [...] I don't know that manpages-dev has a policy on that. Upstream man-pages policy is: yes, document glibc specifics (but give context re portability). [...] Thanks a lot Michael for all the details. BTW, I just came accross:

Bug#487254: manpages-dev: *scanf may set errno to ERANGE

2008-06-23 Thread Stephane Chazelas
On Mon, Jun 23, 2008 at 11:27:39AM +0200, Michael Kerrisk wrote: [...] Also, the %as GNU extension seems not to be documented (it may return ENOMEM) in the man page. It is in the glibc documentation. Have you tried using this? I'm trying to test now, but gcc complains that '%a' expects

Bug#487254: manpages-dev: *scanf may set errno to ERANGE

2008-06-23 Thread Stephane Chazelas
On Mon, Jun 23, 2008 at 12:37:50PM +0200, Michael Kerrisk wrote: [...] NOTES The GNU C library supports a non-standard extension that causes the library to dynamically allocate a string of sufficient size for input strings for the %s and %a[range] conversion

Bug#487254: manpages-dev: *scanf may set errno to ERANGE

2008-06-23 Thread Stephane Chazelas
On Mon, Jun 23, 2008 at 12:37:50PM +0200, Michael Kerrisk wrote: [...] This feature is not available if the program is compiled with cc -std=cc99 or cc -D_ISOC99_SOURCE (unless _GNU_SOURCE is also [...] typo: -std=c99, not cc99. -- Stéphane -- To UNSUBSCRIBE, email to

Bug#487254: manpages-dev: *scanf may set errno to ERANGE

2008-06-23 Thread Stephane Chazelas
On Mon, Jun 23, 2008 at 01:34:04PM +0200, Michael Kerrisk wrote: On Mon, Jun 23, 2008 at 1:31 PM, Stephane Chazelas [EMAIL PROTECTED] wrote: On Mon, Jun 23, 2008 at 12:37:50PM +0200, Michael Kerrisk wrote: [...] This feature is not available if the program is compiled

Bug#487254: manpages-dev: *scanf may set errno to ERANGE

2008-06-23 Thread Stephane Chazelas
On Mon, Jun 23, 2008 at 01:43:39PM +0200, Michael Kerrisk wrote: [...] errno = 0; n = scanf(..., p); if (n == 1) { printf(OK: %s\n, p); free(p); } else if (errno != 0) { perror(scanf); } else { fprintf(stderr, expected letters, not \%s\\n, ...); Well, that error message

Bug#487254: manpages-dev: *scanf may set errno to ERANGE

2008-06-23 Thread Stephane Chazelas
On Mon, Jun 23, 2008 at 01:45:28PM +0200, Michael Kerrisk wrote: On Mon, Jun 23, 2008 at 1:43 PM, Stephane Chazelas [EMAIL PROTECTED] wrote: On Mon, Jun 23, 2008 at 01:34:04PM +0200, Michael Kerrisk wrote: On Mon, Jun 23, 2008 at 1:31 PM, Stephane Chazelas [EMAIL PROTECTED] wrote

Bug#487254: manpages-dev: *scanf may set errno to ERANGE

2008-06-23 Thread Stephane Chazelas
On Mon, Jun 23, 2008 at 01:47:59PM +0200, Michael Kerrisk wrote: Right, here's another version. Could you please have another read through, Stephane Michael, it looks good to me. I suspect it wasn't your intention to leave printf(n=%d, errno=%d\n, n, errno); in though. That

Bug#487254: manpages-dev: *scanf may set errno to ERANGE

2008-06-23 Thread Stephane Chazelas
On Mon, Jun 23, 2008 at 01:52:07PM +0100, Stephane Chazelas wrote: [...] So, %as is not available for instance with: cc -D__STDC_VERSION__=199901L (tcc does set that as a builtin macro http://hg.sharesource.org/mercurialtcc/rev/1e81d5b65878) [...] FYI, and I'm getting off-topic here

Bug#485636: manpages-dev: nanosleep(2) and high resolution timers

2008-06-24 Thread Stephane Chazelas
On Tue, Jun 24, 2008 at 09:10:00AM +0200, Michael Kerrisk wrote: [...] I think it should be worth mentionning that since 2.6.16, on some architectures, the kernel can be configured with high resolution timers which makes nanosleep(2) a lot more accurate and voids the first comment

Bug#485636: manpages-dev: nanosleep(2) and high resolution timers

2008-06-24 Thread Stephane Chazelas
On Tue, Jun 24, 2008 at 11:22:48AM +0200, Michael Kerrisk wrote: Okay -- as a first step to resolving this, I've adjusted the text in time.7, including adding a mention of HRTs. The text that I plan to put in man-pages-3.01 is shown below. Does it look okay to you Stephane? [...] Michael,

Bug#479051: [Pkg-nagios-devel] Bug#479051: nagios3: wrong home directory for the nagios user

2008-05-04 Thread Stephane Chazelas
2008-05-04 12:41:31 +0200, Alexander Wirt: tag 479051 moreinfo thanks Stephane Chazelas schrieb am Friday, den 02. May 2008: Package: nagios3 Version: 3.0.1-1 Severity: normal The nagios user is being added by /usr/sbin/useradd -r -d /var/log/nagios -s /bin/sh -c %{nsusr

Bug#476519: [Pkg-shadow-devel] Bug#476519: shell-mode garbles input

2008-05-04 Thread Stephane Chazelas
On Sun, May 04, 2008 at 10:14:26AM +0800, [EMAIL PROTECTED] wrote: [...] SC Have you tried changing nobody's shell? I don't want to. Then, can you try: su - nobody -c ksh su - nobody -c pdksh su - nobody -c zsh Also, what about: perl -e '$=$=$(=$)=65534; exec sh' perl -e '$=$=$(=$)=65534;

Bug#479406: su fails for users with a POSIX script as their login shell

2008-05-04 Thread Stephane Chazelas
Package: login Version: 1:4.1.1-1 Severity: normal (Note that the same applies to login). With this password entry: test:x:1000:1000:test:/:/tmp/x And /tmp/x being an executable file containing this only line: echo test When logging in as user test, or with su test you get: Cannot

Bug#479051: [Pkg-nagios-devel] Bug#479051: nagios3: wrong home directory for the nagios user

2008-05-04 Thread Stephane Chazelas
2008-05-04 18:50:13 +0200, Alexander Wirt: [...] the thing is that the user here was created with a home directory of /var/log/nagios, so I did a grep -r on the source package and found the line above in the nagios.spec file. nagios.spec? Debian don't uses spec files. You're right, it

Bug#479406: su fails for users with a POSIX script as their login shell

2008-05-05 Thread Stephane Chazelas
BTW, this code (thanksfully disabled on Linux) is wrong: /* Linux handles #! in the kernel, and bash doesn't make sense of #! so it wouldn't work anyway... --marekm */ #ifndef __linux__ /* * It is perfectly OK to have a shell script for a login *

Bug#479764: shell builtin mv fails to move files across devices

2008-05-06 Thread Stephane Chazelas
On Tue, May 06, 2008 at 04:03:03PM +0100, Clint Adams wrote: On Tue, May 06, 2008 at 03:42:08PM +0100, martin f krafft wrote: lapse:~/debian|master|debian.ch% echo $ZSH_VERSION 4.3.6-dev-0+0428 lapse:~/debian|master|debian.ch% zmodload zsh/files lapse:~/debian|master|debian.ch% which mv

Bug#479804: rsh-redone-server: rshd leaves an extra fd open to the stderr socket

2008-05-06 Thread Stephane Chazelas
Package: rsh-redone-server Version: 81-2 Severity: normal Tags: patch rsh -n localhost 'sleep 100 /dev/null /dev/null 21 ' should return immediately, not after 100s. With rshd from rshd-redone-server, it doesn't. This is because rshd forgets to close the fd that has been used to setup the

Bug#479804: rsh-redone-server: rshd leaves an extra fd open to the stderr socket

2008-05-07 Thread Stephane Chazelas
Sorry, ideally, the fix would rather be: --- rshd.c~ 2005-11-26 13:44:17.0 + +++ rshd.c 2008-05-07 08:27:57.0 +0100 @@ -220,9 +220,12 @@ int main(int argc, char **argv) { freeaddrinfo(ai); -

Bug#479984: nagios-plugins: check_ldap doesn't allow empty bases

2008-05-07 Thread Stephane Chazelas
Package: nagios-plugins Version: 1.4.11-2 Severity: normal Hiya, $ /usr/lib/nagios/plugins/check_ldap -H localhost -b '' check_ldap: Please specify the LDAP base doesn't work. For me, a check with an empty base seems like the most obvious thing to do. So I don't understand why it is

Bug#480001: nagios3: spurious dollar signs added to command_lines

2008-05-07 Thread Stephane Chazelas
Package: nagios3 Version: 3.0.1-1 Severity: normal Tags: patch Hiya, In the definition of a command object such as: define command{ command_namemy_test command_lineecho '$xxx' } If the command_line contains an odd number of $'s, then nagios adds an extra one.

Bug#480371: ash: export -p may output incorrect variables

2008-05-09 Thread Stephane Chazelas
Package: ash Version: 0.5.4-9 Severity: normal ~$ env -i '1=' ash -c 'export -p' export 1='' export PWD='/home/chazelas' ~$ env -i '1=' ash -c 'export' export 1='' export PWD='/home/chazelas' $ env -i '=' ash -c 'export' export ='' export PWD='/home/chazelas' ash should report about the 1 and

Bug#476517: grub-pc: improper handling of GRUB_PRELOAD_MODULES in update-grub

2008-04-17 Thread Stephane Chazelas
Package: grub-pc Version: 1.96+20080413-1 Severity: important Hiya, one gets an error if he defines GRUB_PRELOAD_MODULES in /etc/default/grub. This is because of the typo in update-grub that can be fixed with: --- /tmp/update-grub2008-04-17 10:10:49.0 +0100 +++

Bug#476128: 2 minutes timeouts on accessing unpermitted NFS-shares

2008-04-18 Thread Stephane Chazelas
Same here, As I've got an automount on /home and mounts to remote-host:/home/unexisting end up in a EACCESS, that causes a lot of applications to hang. This is a very serious bug to my mind. A simple fix would be: --- /home/stephane/tmp/stropts.c~ 2008-04-18 17:24:17.35563 +0100 +++

Bug#470886: xserver-xorg-input-kbd: repeated KeyPress events when switching VT while pressing a key

2008-03-14 Thread Stephane Chazelas
Package: xserver-xorg-input-kbd Version: 1:1.2.2-3 Severity: normal Hiya, this has been buggering me for a long time, only now I've put a little investigation in it. If, from xorg, I switch to another VT while pressing a key, the original X server keeps sending keypress events to the

Bug#615875: libarchive1: ext2 file attributes/flags not fully supported

2011-02-28 Thread Stephane Chazelas
Package: libarchive1 Version: 2.8.4-1 Severity: normal In libarchive/archive_read_disk_entry_from_file.c, there is code to retrieve ext2 extended file attributes (see chattr(8)) from regular files and directories but it is not enabled because of some missing #includes. Enabling it should only

Bug#615875: libarchive1: ext2 file attributes/flags not fully supported

2011-02-28 Thread Stephane Chazelas
2011-02-28 17:29:32 +, Stephane Chazelas: 2011-02-28 18:24:59 +0100, Andreas Henriksson: [...] Thanks for your bug report. Could you please file this on http://code.google.com/p/libarchive so the upstream authors can contact you directly if they have any questions about the patch

  1   2   >