FYI, bugzilla.clamav.net has been discontinued.
New upstreams bugs:
https://github.com/Cisco-Talos/clamav/issues/1169
(also
https://github.com/Cisco-Talos/clamav/issues/347
https://github.com/Cisco-Talos/clamav/issues/922)
Colour highlighting was intentionally removed when ncal is
invoked as cal, as per
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904839
cal being there only for historical purposes to give the old
style output and with the same API (see also
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=8679
Some additional notes, from discussion on the Ubuntu bugs:
1. dpkg-reconfigure dialogs say in the first dialog:
"The ClamAV suite won't work if it isn't configured".
However, that dialog is not displayed upon install, and
except for
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=97
Package: clamav-daemon
Version: 0.103.2+dfsg-2
Severity: important
Hello,
this is spawned off
https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1930393
where I reported the same bug for Ubuntu. Also affects Debian.
It's a (non-critical) security vulnerability but the issue has
already made pu
2019-03-06 19:25:33 +0100, Michael Biebl:
[...]
> Please consider forwarding it to upstream at
> https://github.com/systemd/systemd as pull request
>
> We usually prefer for patches to be applied upstream first.
[...]
Done:
https://github.com/systemd/systemd/pull/11912
https://github.com/syst
Package: systemd
Version: 241-1
Severity: normal
Tags: patch upstream
Dear Maintainer,
At work, users (in LDAP) have home directories set as
/export/./home/username. The /./ is used for instance by vsftpd
to indicate the location where the users are chrooted into (not
relevant to this bug other t
2018-09-07 23:44:08 +0200, Rene Engelhard:
[...]
> I don't buy this: The autopkgtest of exactly the version you report it
> against:
[...]
Hi Rene,
I can reproduce on a different system. The evidences can also be
found in the source:
See
https://sources.debian.org/src/libnumbertext/1.0-2/debian
Package: libnumbertext-tools
Version: 1.0-2
Severity: normal
$ dpkg -L libnumbertext-tools
[...]
/usr/lib/libnumbertext/spellout
The tool is meant to be invoked by the end user, but is not
located in a directory in $PATH. I would expect it to go in
/usr/bin (and have a corresponding man page in
/
Package: bsdmainutils
Version: 11.1.2
Severity: normal
Tags: patch
Dear Maintainer,
Background: I was trying to use "look -b" on the "have I been
pwned" password database
(https://downloads.pwnedpasswords.com/passwords/pwned-passwords-ordered-2.0.txt.7z)
That file is about 32GiB uncompressed and
It might just be a matter of st.quote being used uninitialised.
The patch below seems to make this particular problem go away.
diff --git a/eval.c b/eval.c
index 5deca57..4b882c1 100644
--- a/eval.c
+++ b/eval.c
@@ -201,6 +201,7 @@ expand(const char *cp, /* input word */
make_magic =
Package: posh
Version: 0.12.6
Severity: important
case xy in
"x"*) echo yes;;
*) echo no;;
esac
outputs "no".
echo "/"*
outputs "/*".
The bug is likely to have been introduced by
https://anonscm.debian.org/cgit/users/clint/posh.git/commit/?id=244887c7559bee1b9766d391aa33d5408b27c77f
so Th
Tags: patch
Note that it does a "kill(0,thesignal)" so would kill the parent
and every other process in its process group.
diff -ur posh/main.c posh-0.12.6.new/main.c
--- posh/main.c 2015-06-07 19:23:37.0 +0100
+++ posh-0.12.6.new/main.c 2018-01-07 10:28:02.113320678 +
@@ -637,7
Not that arithmetic expressions are evaluated in there as in:
[ 1+1 -eq 2 ]
would return true like in ksh93.
Note that in ksh93, things like 010 in test operands are always
treated as decimal even when they're part of arithmetic
expressions.
For hexadecimal however, [ 0x12 -eq 0 ] [ 0x12+1 -eq
Package: posh
Version: 0.12.5
Severity: normal
Dear Maintainer,
In:
[ "$a" -eq "$b" ] or any other numerical comparison operator,
the values of $a and $b are treated as octal if they begin with
0 or hexadecimal if they begin with 0x or 0X (and leading blanks
are ignored)
As per POSIX (see point
2015-06-30 16:45:59 +0200, Vincent Lefevre:
> On 2015-06-30 15:04:17 +0100, Stephane Chazelas wrote:
> > Or use luit that has been designed for that:
>
> However it doesn't work from non-UTF-8 terminals.
Yes, though if you don't use a UTF-8 terminal you won't be ab
2015-06-30 13:30:50 +0200, Vincent Lefevre:
[...]
> > I don't understand what you mean.
> > My point was, applications/systems use different locales. Nothing will
> > change that.
> > Thus when you process output from a remote application on the local
> > system, you must assume that this is happen
2015-06-30 15:04:17 +0100, Stephane Chazelas:
[...]
> ssh -t host luit
>
> (assuming luit is installed on host).
>
> (unfortunately it doesn't seem to support the /new/ Western
> Europe charset iso8859-15).
[...]
Sorry, it does support it, but it seems it fails to dete
2014-12-08 22:22:03 +0100, Stéphane Aulery:
> Le lundi 08 décembre 2014 à 08:37:38, Stephane CHAZELAS a écrit :
> > 2014-12-08 19:50:05 +0100, Stéphane Aulery:
> > >>>> [n1]>&n2Redirect standard output (or fd n1) to the same "open
> > &
2014-12-08 19:50:05 +0100, Stéphane Aulery:
[n1]>&n2Redirect standard output (or fd n1) to the same "open
file description" as on fd n2.
[n1]>&n2Copy fd n2 as stdout (or fd n1)
[n1]>&n2Redirect standard output (or fd n1) to the same
Package: posh
Version: 0.12.3
Severity: normal
Dear Maintainer,
$ env -u a posh -c 'echo $((a))'
posh: : unexpected `end of expression'
$ env a= posh -c 'echo $((a))'
0
I can't see why posh would return an error in the first case and
not the second.
$ env a=1+1 posh -c 'echo $((a))'
2
$ env a=b
I'd say there's at least one bug and it doesn't seem to be fixed
upstreams
(http://sourceware.org/git/?p=glibc.git;a=blob;f=libio/fileops.c;h=e92f85b243496c07d3677b97c785da7f42fb6c38;hb=HEAD#l531)
so you may want to forward to them:
530 count = _IO_SYSWRITE (fp, data, to_do);
531 if (fp->_cu
Note that it's not only upon ENOSPC, EPIPE will do as well:
$ yes | (trap '' PIPE; tr a b) | :
zsh: broken pipe yes |
zsh: segmentation fault ( trap '' PIPE; tr a b; )
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contac
Package: coreutils
Version: 8.21-1
Severity: normal
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
Easiest way to reproduce:
~$ tr a b < /dev/zero > /dev/full
zsh: segmentation fault (core dumped) tr a b < /dev/zero > /dev/full
I first reproduced
I suppose a fix could be:
--- ffproxy~ 2011-11-13 14:04:44.0 +
+++ /etc/init.d/ffproxy 2012-01-12 13:58:45.679406982 +
@@ -60,12 +60,10 @@
fi
update_chroot() {
-if [ ! -d "$FFPROXY_CHROOT" ]; then
-mkdir -p "$FFPROXY_CHROOT"
-fi
+mkdir -p "$FFPROXY_CHROOT"
Package: ffproxy
Version: 1.6-8
Severity: normal
Dear Maintainer,
After installing ffproxy, we see a ffproxy process running as
"nobody" (fine) chrooted in a /var/lib/ffproxy (fine), but with
all the files in there owned and writable by nobody.
$ find /var/lib/ffproxy -ls
2824304 drwxr-xr-x
Package: posh
Version: 0.10
Severity: normal
Dear Maintainer,
$ posh -c 'echo $POSH_VERSION'
POSH_VERSION
While the actual posh version was expected.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing'), (50, 'unstable'), (1, 'experimental')
Arc
Package: c-icap
Version: 1:0.1.6-1
Severity: normal
c-icap doesn't detach from the terminal and doesn't close fds
before going in the background.
stdin/stdout/stderr are left as is. I could see crash messages
in libclamav on the terminal where "service c-icap restart" had
been run.
Also, c-icap
Package: c-icap
Version: 1:0.1.6-1
Severity: normal
Hiya,
The named pipe used to send control requests to the c-icap
server has incorrect permissions. That could even be considered
as a security issue as any user on the system can cause some of
the requests to c-icap to not be delivered to it or
2011-09-06 09:18:57 +0100, Colin Watson:
> On Tue, Sep 06, 2011 at 08:39:24AM +0100, Stephane Chazelas wrote:
> > I do get a segfault as well when doing a grub-setup/grub-install
> > on a mdraid with 1.2 metadata.
> >
> > The segv is in:
> >
> > grub_uti
Package: grub-pc
Version: 1.99-11
Severity: normal
Dear Maintainer,
If setting up a machine (virtual for instance) with a RAID1
array initially created degraded with a missing part, then grub
won't boot (reboots after "loading grub"):
Example:
(I don't think the LVM part is relevant)
truncate -
I do get a segfault as well when doing a grub-setup/grub-install
on a mdraid with 1.2 metadata.
The segv is in:
grub_util_biosdisk_is_floppy() because the disk->id for the root
device is not a bios disk id, but a big number that is the
"array id". The patch below seems to fix it for me, though I
I do get a segfault as well when doing a grub-setup/grub-install
on a mdraid with 1.2 metadata.
The segv is in:
grub_util_biosdisk_is_floppy() because the disk->id for the root
device is not a bios disk id, but a big number that is the
"array id". The patch below seems to fix it for me, though I
Package: posh
Version: 0.10
Severity: normal
$ posh -c 'while :; do ! break; done'; echo $?
0
While it should be 1.
This bug affects all the descendants of the pdksh (pdksh, posh,
mksh on debian at least).
There's a similar bug in
for i in a; do ! continue; done
-- System Information:
Debia
2011-03-17 08:41:28 +0100, Sean Finney:
> On Wed, 2011-03-16 at 21:57 -0600, Raphael Geissert wrote:
> > On 16 March 2011 03:40, sean finney wrote:
> > > On Wed, Mar 16, 2011 at 09:27:29AM +, Stephane Chazelas wrote:
> > >> No, please look carefully
2011-03-16 09:59:55 +0100, sean finney:
> Hi Stephane,
Hi Sean,
> On Tue, Mar 15, 2011 at 04:17:50PM +, Stephane Chazelas wrote:
> > 09,39 * * * * root [ -x /usr/lib/php5/maxlifetime ] && [ -d
> > /var/lib/php5 ] && find /var/lib/php5/ -
Package: php5-common
Version: 5.3.5-1
Severity: normal
/etc/cron.d/php5 has:
09,39 * * * * root [ -x /usr/lib/php5/maxlifetime ] && [ -d
/var/lib/php5 ] && find /var/lib/php5/ -type f -cmin
+$(/usr/lib/php5/maxlifetime) -print0 | xargs -n 200 -r -0 rm
$ ls -dl /var/lib/php5
drwx-wx-w
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?
>
> (If you don't care much about registering with
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
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 be
2010-05-04 16:07:25 +, Gerrit Pape:
> On Tue, Oct 28, 2008 at 04:51:03PM +0000, Stephane Chazelas wrote:
> > Hiya,
> >
> > $ ash -c '. -- --help'
> > .: 1: --: not found
> >
> > The handling of "--" is mandated by POSIX I belei
2010-04-08 09:17:37 +0100, Geoff Clare:
> Johannes Sixt wrote, on 07 Apr 2010:
> >
> > The next question is then, what shall happen when there is no temporary
> > execution environment, i.e., what is the expected output of
> >
> > X=a Y=b; X=$Y Y=$X; echo $X $Y
>
> That's a much simpler case, a
Sorry,
the email address I used to submit the bug is incorrect. It
should have been stephane_chaze...@yahoo.fr.
--
Stephane
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: coreutils
Version: 8.4-1
Severity: normal
File: /usr/bin/uniq
~$ locale charmap
UTF-8
~$ locale collate-codeset
UTF-8
~$ sort .zsh-history|uniq -D|sed -n l
cd Pyr\202n\202es$
cd Pyr\351n\351es$
Both lines are identical except for the invalid UTF-8
characters, uniq reports them as ident
Package: posh
Version: 0.8.4
Severity: normal
$ posh -c 'f() echo test; f'
test
Same output for all the other Bourne-like shells but bash.
$ bash -c 'f() echo test; f'
bash: -c: line 0: syntax error near unexpected token `echo'
bash: -c: line 0: `f() echo test; f'
which makes that construct no
2009-07-20 16:03:35 +0200, Nicolas François:
[...]
> login is the easiest, su is more complex because the behavior of
> "su -c " must be defined in this case. So I will just make it as
> "/bin/sh -c "
[..]
> + if (access (file, R_OK|X_OK) == 0) {
> + /*
> + * Assume th
2009-07-18 21:26:56 +0200, Nicolas François:
> Ping
Sorry, forgot to reply to your earlier email.
> Any opinion on this?
>
> My current preference would be to close the bug.
> It could also be tagged wontfix: I'm not sure the feature is that useful,
> and switching to execlp/execvp/system could
2009-06-09 12:17:04 +0100, Stephane Chazelas:
> 2009-06-09 11:13:25 +0100, Stephane Chazelas:
> [...]
> > that patch is still wrong.
> >
> > The first time a HUP is received, we run the code in the trap
> > and call wait which will wait for both the refresh
2009-06-09 11:13:25 +0100, Stephane Chazelas:
[...]
> that patch is still wrong.
>
> The first time a HUP is received, we run the code in the trap
> and call wait which will wait for both the refresh command and
> the mysqld one.
>
> But we won't return from that trap
2009-05-12 12:21:39 -0400, Mathias Gug:
> Here is a patch applied in Ubuntu that adresses the issue.
>
> The problem comes from the fact that mysqld_safe starts mysqld and then
> waits for its crash. However installing a trap for SIGHUP makes the wait
> command return immediately when a SIGHUP is
Package: cron
Version: 3.0pl1-105
Severity: normal
Hiya,
The crontab command from the cron package seems not to be POSIX
conformant:
$ crontab
crontab: usage error: file name must be specified for replace
[...]
$ POSIXLY_CORRECT=1 crontab
crontab: usage error: file name must be specified for re
On Tue, Dec 30, 2008 at 12:16:49AM +0100, Richard Hartmann wrote:
> Please don't CC 276...@bugs.debian.org any more -- my fault for mixing
> two bugs into one email. Won't happen again.
>
> On Mon, Dec 29, 2008 at 22:19, Stephane Chazelas
> wrote:
>
> > That&#x
On Mon, Dec 29, 2008 at 09:46:07PM +0100, Richard Hartmann wrote:
[...]
> 2) Unexpected behaviour when stopping a job in a command chain[3]
>
> Consider this:
>
> echo one && sleep 10 && echo two
>
> When stopping `sleep 10`, `echo two` will never be executed, no matter in
> what way you revive
On Tue, Dec 30, 2008 at 12:16:49AM +0100, Richard Hartmann wrote:
> Please don't CC 276...@bugs.debian.org any more -- my fault for mixing
> two bugs into one email. Won't happen again.
>
> On Mon, Dec 29, 2008 at 22:19, Stephane Chazelas
> wrote:
>
> > That&#x
On Mon, Dec 29, 2008 at 09:46:07PM +0100, Richard Hartmann wrote:
[...]
> 2) Unexpected behaviour when stopping a job in a command chain[3]
>
> Consider this:
>
> echo one && sleep 10 && echo two
>
> When stopping `sleep 10`, `echo two` will never be executed, no matter in
> what way you revive
Package: cups
Version: 1.3.8-1lenny2
Severity: normal
Below is a wireshark capture of a client (nagios) doing an HTTP
request to cups. The client uses HTTP 1.1 and includes the
"Connection: close" header meaning that he wants that request to
be the last one. cups replies with a "Connection: keep-
Package: ash
Version: 0.5.4-12
Severity: normal
Hiya,
$ ash -c '. -- --help'
.: 1: --: not found
The handling of "--" is mandated by POSIX I beleive.
With ksh, pdksh, bash and in a POSIX script in general as POSIX
allows any "." implementation to recognise options, you have to
use:
. -- "$1"
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 p
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]
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()
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 $smbclientopti
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 -
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
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 fir
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 ge
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 p
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 Chaz
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", ...);
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 ava
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 [EMA
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] conversio
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'
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 accros
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 pro
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 th
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 requ
disk_smb.dpatch which fixes 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
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 kn
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
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 a
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 curr
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
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.
~$
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
> &
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 'f
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;
>
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 SU
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 ${=}'
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)
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
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
> &
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 conforman
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 "se
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 si
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 so
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,
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 some
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 1
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' **/
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
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 o
1 - 100 of 156 matches
Mail list logo
