Hi,
my timezone is CEST; we switched from CET today.
% TZ=Europe/Budapest LC_TIME=C date --date 'tomorrow 2:30'
date: invalid date ‘tomorrow 2:30’
2:30 would be invalid today (2:00am became 3:00am), but it exists tomorrow, and
date(1) can print that date if I request it in a different way:
%
On Fri, Jan 05, 2024 at 07:04:02AM +, 陈 晟祺 wrote:
Hi,
> > zfs-dkms is the failsafe in case the zfs-modules- package is
> > *not* installed
> > (for example, because this is the first slow box I'm installing this kernel
> > or this version of
> > zfs-dkms on and I don't yet have a
Package: squid
Version: 6.3-1
Severity: grave
Tags: security patch
X-Debbugs-Cc: Debian Security Team
Hi,
https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2023-2725
links to a bunch of squid advisories, three of which have CVSS scores of 9+:
On Mon, Oct 02, 2023 at 04:00:57PM -0400, Michael Jeanson wrote:
Hi,
> Can you open a bug upstream? I would prefer to go with a fix approved by
> upstream.
Sure, will do.
> Also I'm not sure I understand under which circumstances the content of
> '$value' could be controlled by an
OK, that quick fix will work for whitespace but still break on apostrophes.
How about using the escapeshellparam sub?
https://github.com/jimsalterjrs/sanoid/blob/61000c9da2f8762424ba2de8a49abb1b7ec5154d/syncoid#L2070
Or, better yet, replace that sub with this:
Package: sanoid
Version: 2.2.0-1
Severity: important
Tags: upstream patch
Hi,
line 496 of syncoid reads
$recvoptions .= " -o $key=$value";
this string is then apparently passed to a shell, which will split $value into
words on whitespace, causing the zfs command line to become invalid at best
Hi,
I've tried a kerberos-enabled build of freerdp2; it didn't actually work. I
asked the freerdp people in #freerdp on irc.oftc.net and they said to use
FreeRDP3:
14:49 -> hi, I'm trying to use kerberos authentication to connect to a Windows
server using xfreerdp (compiled with gssapi
On Mon, Sep 04, 2023 at 08:19:45AM +0200, Petter Reinholdtsen wrote:
> [Andras Korn]
> > I have computers that take forever to build kernel modules; therefore,
> > while I have zfs-dkms installed as a failsafe, I also strive to always
> > install zfs-modules- preemptively.
&g
Package: zfs-dkms
Version: 2.1.12-2
Severity: normal
Hi,
I have computers that take forever to build kernel modules; therefore, while I
have zfs-dkms installed as a failsafe, I also strive to always install
zfs-modules- preemptively.
Unfortunately, the zfs-dkms postinst still causes the zfs
Package: dkms
Version: 3.0.11-3
Severity: normal
Hi,
I have computers where I install both zfs-dkms and sometimes
zfs-modules- packages.
When zfs-modules- is installed, zfs-dkms fails postinst:
[...]
zzstd.ko:
Running module version sanity check.
Module version 1.4.5a-2.1.12-2 for zzstd.ko
Package: cron
Version: 3.0pl1-174
Severity: important
Hi,
with /bin gone from the default PATH in /etc/crontab (due to #1042894), cron
will no longer find run-parts(8), which is in /bin, unless /bin is merged into
/usr/bin.
I ran into this on dozens of systems that were upgraded to sid
Package: tmpreaper
Version: 1.6.17
Severity: normal
Hi,
having libpam-tmpdir installed results in PAM creating a
/tmp/user/ directory for every user when they start a
session, setting TMP and TMPDIR to this directory.
Long-running processes such as web applications started e.g. via sudo -u
Package: slapd-contrib
Version: 2.5.13+dfsg-5
Severity: wishlist
Hi,
please build and ship contrib/slapd-modules/ppm. It greatly enhances the
functionality of the password policy overlay by allowing the user to implement
semi-complex password policies (such as "have characters from at least 4
On Wed, Jun 21, 2023 at 10:18:13AM +0300, David Bremner wrote:
> > I began using a revision tracking system for some configfiles. This
> > involved replacing /etc/nullmailer with a symlink to a directory
> > within the local working copy.
>
> I don't know if it's practical for you, but as a
Package: nullmailer
Version: 1:2.2-3+b1
Severity: normal
Hi,
I began using a revision tracking system for some configfiles. This involved
replacing /etc/nullmailer with a symlink to a directory within the local
working copy.
I noticed that locally generated mail was suddenly referencing
Hi,
possibly related: since upgrading to 112.0, some custom fonts set by websites
are no longer rendered.
For example, on https://www.teletal.hu/etlap/16, there is supposed to be a
leftmost column of row labels in the table, saying "RE1", "RE2", "A1", "A2" and
so on.
If the setting "Allow
On Tue, Mar 28, 2023 at 01:10:36AM +0200, Lorenzo wrote:
Hi,
> Please follow up and let me know if my idea would solve this issue or at
> least improve the situation from your point of view:
> >
> > Checking for /etc/sv/$name and skipping initscripts if those directories
> > exist is wrong
Package: unattended-upgrades
Version: 2.9.1+nmu3
Severity: wishlist
Hi,
not all flavours of shutdown(8) support a time argument; for example, runit's
only supports 'now' or no time.
When unattended-upgrades tries to schedule a reboot on runit systems,
shutdown(8) prints an error, causing
fwiw, psmisc 23.5-3 still works even if the kernel doesn't support statx().
The changelog for 23.6 says "fuser: Use modern statn where possible", but it's
regrettably also used where not possible.
András
--
Is 6 afraid of 7, 'cause 7 8 9?
Hi,
it seems to me that in postinst, instead of
if $do_systemd
then
systemctl start pmcd.service >/dev/null
systemctl start pmlogger.service >/dev/null
elif which invoke-rc.d >/dev/null 2>&1
then
invoke-rc.d pmcd start
invoke-rc.d pmlogger start
else
/etc/init.d/pmcd start
Package: psmisc
Version: 23.6-1
Severity: normal
Hi,
fuser(1) will call statx():
statx(0>, "/", AT_STATX_DONT_SYNC|AT_NO_AUTOMOUNT,
STATX_TYPE|STATX_INO, 0x7fffb96603a0) = -1 ENOSYS (Function not implemented)
which is not avilable on kernels before, I think, 4.11.
When that fails, fuser(1)
Package: zsh
Version: 5.9-3
Severity: normal
Tags: patch
Hi,
this was last reported as #951457.
Apparently this change (from zsh changelog):
2020-01-06 Daniel Shahaf
* 45213: README, configure.ac: Make --enable-gdbm default to
false, rather than default to true with an
On Thu, Feb 02, 2023 at 12:27:04AM +0100, Lorenzo wrote:
Hi,
> > /etc/runit/2 ships with this snippet:
> >
> > mkdir -p /run/runit/supervise
> > mkdir -p /run/runit/sv
> > mount -t tmpfs -o size=20M,mode=0755 runtimesv /run/runit/sv
> > cp -a /etc/sv/* /run/runit/sv/ #TODO do this with
> >
Package: runit
Version: 2.1.2-53
Severity: minor
Hi,
/etc/runit/2 ships with this snippet:
mkdir -p /run/runit/supervise
mkdir -p /run/runit/sv
mount -t tmpfs -o size=20M,mode=0755 runtimesv /run/runit/sv
cp -a /etc/sv/* /run/runit/sv/ #TODO do this with 'CPSV_DIR=/run/runit/sv cpsv
--sync'
Package: runit
Version: 2.1.2-53
Severity: normal
Tags: patch
Hi,
/etc/runit/2 ships with this snippet:
if [ "$runsv_dir" != solo ] || [ ! -e /etc/runit/no.emulate.sysv ]; then
/lib/runit/async-timeout /lib/runit/run_sysv_scripts
'/etc/rc2.d'
fi
This means that
On Wed, Nov 16, 2022 at 02:03:14PM +0100, Lorenzo wrote:
> > > lsof /dev/log >/dev/null || exit 1
> >
> > I think
> >
> > fuser /dev/log >/dev/null 2>/dev/null || exit 1
> >
> > is more efficient, but there is a problem with both approaches: the process
> > that is listening on /dev/null may
On Tue, Nov 15, 2022 at 10:00:43PM +0100, Salvatore Bonaccorso wrote:
Hi,
> > Try something like this in /lib/udev/rules.d/60-nfs.rules:
> >
> > ACTION=="add", SUBSYSTEM=="module", KERNEL=="sunrpc", \
> > RUN+="/sbin/sysctl -q --pattern ^sunrpc --system"
> > ACTION=="add",
On Mon, Oct 24, 2022 at 11:18:03AM +0200, Andras Korn wrote:
Hi,
> unfortunately the bug is still not fixed despite the NMU; while sgdisk
> doesn't print errors anymore, it also doesn't actually perform the requested
> operations.
I can no longer reproduce the problem. I don't
Hi,
> the check could be just something like
>
> lsof /dev/log >/dev/null || exit 1
I think
fuser /dev/log >/dev/null 2>/dev/null || exit 1
is more efficient, but there is a problem with both approaches: the process
that is listening on /dev/null may be invisible to us, because it may be
On Wed, Nov 02, 2022 at 01:45:24PM +0100, Lorenzo wrote:
Hi,
> Am I correct that this is not a regression introduced with recent changes to
> runit? [relevant to understand if I have to revert something in case I can't
> fix this before the freeze]
Yes. I just started using the default config
On Fri, Oct 28, 2022 at 03:07:07PM +0200, Lorenzo wrote:
Hi,
> > Package: runit
> > Version: 2.1.2-50
> > Severity: normal
> >
> > Hi,
> >
> > /lib/runit/run_sysv_scripts has this:
> >
> > for script in "$initdir/$rX"* ; do
> > [ ! -x "$script" ] && continue
> > path=$(realpath
Package: runit
Version: 2.1.2-50
Severity: normal
Hi,
/lib/runit/run_sysv_scripts has this:
for script in "$initdir/$rX"* ; do
[ ! -x "$script" ] && continue
path=$(realpath "$script")
name=${path##*/}
# Special case for wicd. Runscript is called "wicd-daemon",
Package: runit
Version: 2.1.2-50
Severity: minor
Tags: patch
Hi,
I'm not satisfied with this bit from /etc/runit/1:
--- 8< ---
if [ -f /etc/runit/native.boot.run ] || [ -n "$bootrun" ]; then
bootrun=1
fi
if [ -d /etc/runit/boot-run ] && [ ! -z $bootrun ]; then
for f in
Hi,
unfortunately the bug is still not fixed despite the NMU; while sgdisk doesn't
print errors anymore, it also doesn't actually perform the requested operations.
See e.g.
# sgdisk --zap-all /dev/sda
Creating new GPT
On Fri, Oct 21, 2022 at 03:11:27PM +0200, Marco d'Itri wrote:
Hi,
> > I thought --ignore-install was completely broken, but no, because without
> > it, the output contains *more* "install" lines:
> What you are actually seeing is that --ignore-install is applied only to
> the nfs module (the
Package: kmod
Version: 30+20220905-1
Severity: important
Hi,
I noticed that the sunrpc module was strangely absent from my initramfs, which
resulted in a failure to netboot (which is my justification for the severity).
Upon examination, it turns out that the way module dependencies are worked
Package: joe
Version: 4.6-1+b1
Severity: important
Hi,
as of recently, if I start screen (or tmux, doesn't seem to matter) on a Linux
host, then use lxc-attach to enter a running LXC container, and start joe
inside that container, the terminal behaves in a hard to describe, but
completely
On Mon, Jul 11, 2022 at 10:47:26AM +0300, Martin-Éric Racine wrote:
> On Thu, 6 Jan 2022 18:38:47 +0100 Michael Biebl wrote:
> > On 06.01.22 17:26, Andras Korn wrote:
> > > Package: systemd-timesyncd
> > > Version: 249.7-1
> > > Severity: normal
> > >
Package: tmpreaper
Version: 1.6.17
Severity: wishlist
Hi,
I think you should add something like
[ -r /etc/default/tmpreaper ] && . /etc/default/tmpreaper
at the bottom of /etc/tmpreaper.conf.
Currently, every upgrade that adds some new setting to tmpreaper.conf
requires the user to re-edit
On Thu, Mar 24, 2022 at 01:05:34AM +0100, Lorenzo wrote:
> [1] I'll deal with this in a separate bug, but just to give you an idea:
> why divert start-stop-daemon is better than diverting invoke-rc.d
> and update-rc.d? Or, another example, why not abuse the ancient
> policy-rc.d hack?
I think
Sorry, naturally I found a typo in the script just after sending it:
Index: start-stop-daemon.runit
===
--- start-stop-daemon.runit (revision 1347)
+++ start-stop-daemon.runit (working copy)
@@ -71,7 +71,7 @@
read -A cmdline
Package: runit
Version: 2.1.2-45
Severity: wishlist
Hi,
Back in 2012 I sent Gerrit a start-stop-daemon.runit script (see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678985) that could be used
as a drop-in replacement for the real start-stop-daemon. It's a fairly
feature complete wrapper
On Thu, Feb 24, 2022 at 12:26:51PM +0100, Lorenzo wrote:
> > However, if there were a natural-language explanation or flowchart, I
> > think I could summarize it succinctly in a manner appropriate for the
> > man page, within a day.
> >
> > Alas, that's all the help I can offer at the moment.
>
On Tue, Feb 22, 2022 at 02:36:23PM +0100, Lorenzo wrote:
> > On Mon, 19 Apr 2021 09:45:53 +0200
> > Andras Korn wrote:
> >
> > > Additionally, the documentation as it is now is clear and
> > > straightforward, with few special cases; while the actual beh
FWIW, this is now fixed in the latest upstream master:
https://github.com/dell/dkms/pull/193/commits/775a3389ebbafb4fb5d59747667e604cf4f4d903
András
--
Crime is merely politics without the excuses.
Package: systemd-timesyncd
Version: 249.7-1
Severity: normal
Tags: upstream
Hi,
I noticed that it took a while for the network to become available after my
laptop wakes up from suspend.
I traced the problem to systemd-timesyncd.
I use dhcpcd5, which ships
On Thu, Jan 06, 2022 at 01:07:01AM +0100, lorenzo wrote:
Hi,
> > You now have two flag files and unconditinally use
> > /lib/runit.runlevel.6 first if it exists, even if
> > /lib/runit.runlevel.0 also exists and is newer.
>
> Please look at
>
On Sun, Jan 02, 2022 at 11:45:27PM +0100, Lorenzo wrote:
Hi,
> > I'd argue that introducing stricter requirements on the existence and
> > correct mode of /run/runit.reboot that apply over the whole uptime of
> > the system is a more dangerous and invasive change than introducing a
> > new
On Thu, Dec 30, 2021 at 10:02:55AM +0100, Andras Korn wrote:
> On Wed, Dec 29, 2021 at 03:07:38AM +0100, Lorenzo wrote:
>
> > I'm going to accept a fix for this issue, but I prefer to not have to
> > parse a file and also to not add another flag file only for this, if
On Wed, Dec 29, 2021 at 03:07:38AM +0100, Lorenzo wrote:
> I'm going to accept a fix for this issue, but I prefer to not have to
> parse a file and also to not add another flag file only for this, if
> it's possible.
Well, getting the first character from a file and printing it verbatim is
On Tue, Dec 28, 2021 at 03:16:30PM +0100, Andras Korn wrote:
> If /sbin/runlevel looked like this instead:
>
> #!/bin/sh
> # This only does anything useful if /etc/runit/3 updates /run/runit.runlevel
> before starting stop scripts
> if [ -s /run/runit.runlevel ]; then
>
Package: runit-init
Version: 2.1.2-43
Severity: normal
Tags: patch upstream
Hi,
currently /sbin/runlevel always prints "2 N", which is fine most of the time.
However, runit can invoke initscripts that change behaviour based on
runlevel; for example, the kexec initscript from the kexec package
On Sat, Sep 04, 2021 at 05:38:50PM +0200, lorenzo wrote:
> > Not wanting to invoke sync() on shutdown is a permanent property of a
> > system, not an ephemeral one. Thus, the flag file for this behaviour
> > should be in a permanent location (like /etc/runit, where it
> > originally was), not
Package: dstat
Version: 0.7.4-6.1
Followup-For: Bug #942382
Hi,
there seems to be a fork of dstat called dool, with some recent commits
indicating that it's still being developed:
https://github.com/scottchiefbaker/dool
While unfortunately, #942382 is still present in it, maybe Debian could
Package: runit
Version: 2.1.2-42
Severity: normal
Hi,
I'm the guy who originally submitted the patch to support a 'nosync' flag
file to avoid syncing on shutdown.
I noted with some amazement in the changelog for version 2.1.2-42 that this
file had been moved to /run sometime in the past, with
Package: zfs-dkms
Version: 2.0.3-9
Severity: wishlist
Hi,
https://github.com/openzfs/zfs/releases/tag/zfs-2.1.0 has been out for more
than a month.
It would be great if it could be packaged for Debian because it contains many
interesting new features.
Thanks!
-- System Information:
Debian
On Fri, Jun 11, 2021 at 09:59:51PM +0200, Pierre-Elliott Bécue wrote:
Hi,
> > FWIW, both host and guest use runit, so systemd is not involved; runit
> > doesn't interfere with cgroups or capabilities on its own in any way.
>
> It's not possible if the init in the container is systemd, as far
Package: libc6
Version: 2.31-11
Severity: normal
Hi,
due to
https://salsa.debian.org/glibc-team/glibc/-/commit/6ddfa57577af0d96df9ddd7be401f5ce9a9bcc0f
(a commit from 2004) the preinst script for glibc checks whether the "z" in
the "x.y.z" of the kernel version is less than 255. If yes, the
On Sat, Apr 10, 2021 at 11:11:05PM +0200, Lorenzo wrote:
Hi,
> > runsv(8) says:
> >
> > CUSTOMIZE CONTROL
> >For each control character c sent to the control pipe, runsv
> > first checks if service/control/c exists and is executable. If so, it
> >starts service/control/c and
Package: runit
Version: 2.1.2-39.1
Severity: normal
Tags: upstream
Hi,
runsv(8) says:
CUSTOMIZE CONTROL
For each control character c sent to the control pipe, runsv first
checks if service/control/c exists and is executable. If so, it
starts service/control/c and waits for
Hi,
I hit the same issue.
I upgraded from 1:4.0.4-6 to 1:4.0.5-2, and from kernel 5.9.0-4-amd64 to
5.10.0-2-amd64, and some of my containers that used to work before don't work
anyomre. The ones that still work don't drop sys_admin.
stracing lxc-start I see this:
openat2(33,
you still try
to use TLS is unlikely to be useful, I think a loud warning to stderr would
be appropriate in this case.
> On Wed, Jan 13, 2021 at 01:44:07PM +0100, Andras Korn wrote:
> > OK, looking further, part of the problem is that I didn't have
> > libldap-common ins
On Tue, Jan 12, 2021 at 10:47:22AM -0800, Ryan Tandy wrote:
> > On 2021-01-12 Andras Korn wrote:
> > > I think I shouldn't need to specify `ldap_tls_cacert =
> > > /etc/ssl/certs/ca-certificates.crt` when using a Debian package, since
> > > this is the default lo
On Tue, Jan 12, 2021 at 10:47:22AM -0800, Ryan Tandy wrote:
Hi,
thanks for clearing up some misunderstandings.
> On Tue, Jan 12, 2021 at 07:04:41PM +0100, Andreas Metzler wrote:
> > On 2021-01-12 Andras Korn wrote:
> > > I think I shouldn't need to specify `ldap_tls_cacer
Package: libgnutls30
Version: 3.7.0-3
Severity: wishlist
Hi,
I was just bitten by https://github.com/SSSD/sssd/issues/5444.
Briefly:
* sssd relies on libldap to query LDAP servers.
* libldap can be linked against libssl (openssl) or gnutls for SSL/TLS support.
* libssl supports an
Package: socklog
Version: 2.1.0-8.1
Severity: normal
Hi,
it's entirely valid and possible to run socklog to handle locally generated
logs and e.g. syslog-ng to handle remote syslog clients.
The new Conflicts: in the socklog package makes this unnecessarily hard in
an attempt to prevent people
Package: clsync
Version: 0.4.5-1
Severity: normal
Hi,
with clsync 0.4.2-1, the documented "--splitting process" or
"--splitting=process" argument worked.
In the current version, it gives the error message
Error: argument "process" can't be parsed as a number
Error: Unable to process option
On Sat, Mar 21, 2020 at 10:34:24AM +0100, David Kalnischkies wrote:
> On Fri, Mar 20, 2020 at 03:41:06PM +0100, Andras Korn wrote:
> > with the sources.list entry:
> >
> > deb http://winswitch.org/beta/ buster main
>
> While the error message certainly doesn't hel
Package: apt
Version: 2.0.0
Severity: normal
Hi,
with the sources.list entry:
deb http://winswitch.org/beta/ buster main
apt-get as of 2.0 update prints the unhelpful error message:
E: Unable to parse package file (1)
apt 1.8.4 has no problem with this repository.
I could only find out
On Mon, Mar 02, 2020 at 01:45:26PM -0500, Marvin Renich wrote:
Hi,
> I don't have a github account, and do not wish to get one for this.
> Will someone (Debian maintainer for neomutt, or someone else interested
> in this bug) please file this with upstream as a separate bug, pointing
> out that
On Mon, Mar 02, 2020 at 03:18:54PM +0100, Andreas Henriksson wrote:
> > Your rationale for downgrading the severity of an issue like this is that it
> > doesn't bother you personally?
>
> My rationale, if you must know, is that if this is an important issue,
> then the people who consider it an
On Mon, Mar 02, 2020 at 02:22:44PM +0100, Andreas Henriksson wrote:
Hi,
> > when mutt prompts for something (e.g. To: address, Subject etc.) it
> > previously was possible to just keep pressing backspace until whatever
> > default text was there disappeared.
> >
> > As of this version, it's
Package: rawtherapee
Version: 5.7-1
Severity: wishlist
Hi,
5.8 was released on February 4. Please package it.
No packaging changes seem necessary from 5.7 (at first glance).
Thanks!
András
-- System Information:
Init: runit (via /run/runit.stopit)
Package: zsh
Version: 5.7.1-1+b1
Severity: wishlist
Hi,
zshmodules(1) mentions the "zsh/db/gdbm" module, but it's not actually shipped
by the package:
% zmodload zsh/db/gdbm
zsh: failed to load module `zsh/db/gdbm':
/usr/lib/x86_64-linux-gnu/zsh/5.7.1/zsh/db/gdbm.so: cannot open shared object
Package: trac
Version: 1.2.3+dfsg-1
Severity: normal
Tags: l10n
Hi,
trac 1.2 contained /usr/lib/python2.7/dist-packages/trac/locale/de, but trac
1.2.3+dfsg-1 no longer does.
This, naturally, breaks German localization.
The cause is likely this (happens during package build):
catalog
Package: virt-what
Version: 1.19-1
Severity: normal
Tags: patch
Hi,
This is broken in two ways:
# Check for Linux-VServer
if test -e "${root}/proc/self/status" \
&& cat "${root}/proc/self/status" | grep -q "VxID: [0-9]*"; then
echo linux_vserver
if grep -q "VxID: 0$"
Package: localepurge
Version: 0.7.3.8
Severity: wishlist
Hi,
dpkg-repack fails when localepurge is in use (see #947951).
If dpkg-repack doesn't get fixed, a possible workaround would be to have
localepurge remove entries from /var/lib/dpkg/pkgname.list as it deletes the
files.
I'm not sure how
Package: dpkg-repack
Version: 1.46
Severity: normal
Hi,
the localepurge package can be used to automatically remove unneeded locale
files (and thereby conserve disk space as well as inodes).
dpkg-repack used to just print warnings for non-existent files, but
currently it fails on such packages
Package: neomutt
Version: 2019+dfsg.1-1
Severity: normal
Hi,
when mutt prompts for something (e.g. To: address, Subject etc.) it
previously was possibly to just keep pressing backspace until whatever
default text was there disappeared.
As of this version, it's possible to keep erasing back
Hi,
I just stumbled on this bugreport.
I'm a happy pm-utils user and would like the package to stick around. I use
it on dozens of computers ranging from servers to desktops to laptops.
>From reading the bugreport, there doesn't appear to be any identifiable,
specific, actionable reason for
Hi,
I just encountered the same problem.
I'm fairly certain the root cause is that the game assumes some specific
named font is available, and fails when it isn't (i.e. missing dependency).
I looked at it using xtruss
(https://www.chiark.greenend.org.uk/~sgtatham/xtruss/) and it seems to try
to
On Wed, Jun 26, 2019 at 12:18:25PM +0200, Andras Korn wrote:
> > > I just wrote this script:
> > > https://gist.github.com/akorn/51ee2fe7d36fa139723c851d87e56096 and thought
> > > it might be a good addition to moreutils.
> > >
> > > It caches th
On Tue, Jun 25, 2019 at 08:22:12PM +0200, Nicolas Schier wrote:
Hi,
> > I just wrote this script:
> > https://gist.github.com/akorn/51ee2fe7d36fa139723c851d87e56096 and thought
> > it might be a good addition to moreutils.
> >
> > It caches the stdout, stderr and exit status of arbitrary
Package: moreutils
Version: 0.62-1
Severity: wishlist
Hi,
I just wrote this script:
https://gist.github.com/akorn/51ee2fe7d36fa139723c851d87e56096 and thought
it might be a good addition to moreutils.
It caches the stdout, stderr and exit status of arbitrary commands for a
configurable length
Package: rsync
Version: 3.1.3-6
Severity: wishlist
Tags: upstream
Hi,
according to strace -c, getxattr() and similar calls can take up a lot of
runtime (around ten percent) if there are many files to be synced and other
stuff (I/O, network) is reasonably fast.
It would make sense for rsync to
On Tue, Mar 12, 2019 at 06:37:45PM +, Dmitry Bogatov wrote:
Hi,
> [2019-03-11 16:24] Lorenzo Puliti
> > Package: runit-init
> > Version: 2.1.2-25helpers1
> > Followup-For: Bug #919699
> >
> > Hi,
> >
> > >I am okay with accepting patch to implement writing `wtmp' entry, if it
> > >is
On Mon, Mar 11, 2019 at 06:12:06PM +, Dmitry Bogatov wrote:
> > On Fri, Mar 08, 2019 at 02:39:47PM +, Dmitry Bogatov wrote:
> > > [2019-03-07 12:57] Andras Korn
> > > > part 1 text/plain 218
> > > > Sorry, I sent an
On Fri, Mar 08, 2019 at 02:39:47PM +, Dmitry Bogatov wrote:
Hi,
> [2019-03-07 12:57] Andras Korn
> > part 1 text/plain 218
> > Sorry, I sent an earlier version of the patch by mistake.
> >
> > I'm attaching the correct one, which I te
Package: runit-init
Version: 2.1.2-22
Severity: critical
Hi,
The supplied "/etc/runit/1" calls "/lib/runit/run_sysv_scripts /etc/rcS.d"
during boot.
/lib/runit/run_sysv_scripts runs under "sh -eu", which has the effect that
if any initscript exits unsuccesfully, all subsequent scripts are
Sorry, I sent an earlier version of the patch by mistake.
I'm attaching the correct one, which I tested and which works for me.
András
--
Reality is that which, when you stop believing in it, doesn't go away.
diff --git a/runit-2.1.2/man/runit.8 b/runit-2.1.2/man/runit.8
index
Package: runit
Version: 2.1.2-22
Severity: wishlist
Tags: upstream
Hi,
currently lxc can't cleanly shutdown a container running runit as its init
system, because all it can do to bring about a shutdown is send signals to
init (sigpwr by default), and runit requires additional steps to initiate a
On Sat, Feb 02, 2019 at 11:00:30AM +0100, Julien Cristau wrote:
Hi,
> > as long as mercurial-common is installed, the postgres and sqlite db
> > backend driver of Trac won't load:
> >
> > 2019-01-31 08:58:49,372 Trac[loader] ERROR: Skipping "trac.db.postgres =
> > trac.db.postgres_backend":
On Wed, Jan 30, 2019 at 08:48:34PM +, Dmitry Bogatov wrote:
> > > What is so bad about cluttering environment of daemon?
> >
> > Normally you'd want to avoid passing unnecessary environment variables to
> > daemons. Maybe they'll affect its operation in some way; maybe they'll
> > affect a
Package: mercurial-common
Version: 4.8.2-1
Severity: important
Hi,
as long as mercurial-common is installed, the postgres and sqlite db backend
driver of Trac won't load:
2019-01-31 08:58:49,372 Trac[loader] ERROR: Skipping "trac.db.postgres =
trac.db.postgres_backend":
Traceback (most
On Sat, Jan 26, 2019 at 10:17:05AM +, Dmitry Bogatov wrote:
Hi,
> > I believe instead of
> >
> > rm /etc/service/getty-@TTY@
> >
> > you should do
> >
> > rm "$(pwd)"
> >
> > because then it won't matter what the service is called and where the
> > runsvdir root is (/etc/service or somewhere
On Tue, Jan 22, 2019 at 07:16:43PM +, Dmitry Bogatov wrote:
Hi,
> > (Alternatively, the getty run scripts could start with something like this:
> >
> > [ -c /dev/ttyX ] || rm /etc/service/getty-ttyX
> >
> > and /etc/runit/1 could re-create these symlinks, just to be absolutely sure.
> >
> >
On Wed, Nov 28, 2018 at 06:47:59PM +, Dmitry Bogatov wrote:
Hi,
sorry, didn't look at bug mail for a while.
> > However, whenever the getty-run package is installed in a vserver, I have to
> > manually remove the /service/getty-tty* symlinks.
> >
> > Can you please modify the postinst
Package: runit-init
Version: 2.1.2-22
Severity: wishlist
Tags: upstream
Hi,
the initscripts package ships /etc/init.d/umountnfs.sh, which is started on
shutdown and invokes "halt -w", which writes a shutdown record to
/var/log/wtmp.
The halt(8) binary shipped with runit-init, however, ignores
Package: getty-run
Version: 2.1.2-18
Severity: wishlist
Hi,
I use runit as init extensively in linux-vserver guests which don't have
console devices and thus can't run getty.
Ideally, I wouldn't even have to install the getty-run package, but I
understand it's there to help avoid people
Package: runit-init
Version: 2.1.2-18
Severity: normal
Hi,
sometime in the past year or so, you changed /etc/runit/2 so it sets a PATH
that no longer contains /usr/local/sbin and /usr/local/bin.
I think this is wrong; those are standard locations for locally installed
binaries, and they should
1 - 100 of 271 matches
Mail list logo
