Bug#979617: tcplay: VeraCrypt support
Dear maintainer, tc-play 3.3 seems to build fairly cleanly on bullseye from its tag/release tarball [0]. It'd be *really* nice to have in Debian to be able to handle VeraCrypt volumes. [0]: https://github.com/bwalex/tc-play/archive/v3.3.tar.gz -- with best regards: - Johannes Truschnigg ( johan...@truschnigg.info ) www: https://johannes.truschnigg.info/ phone: +43650217 xmpp: johan...@truschnigg.info signature.asc Description: PGP signature
Bug#1018144: sssd-ad: Active Directory dynamic DNS updates broken without bind9-dnsutils installed
Package: sssd-ad Version: 2.4.1-2 Severity: normal Dear Maintainer, sssd-ad supports dynamically updating DNS recource records on Active Directory-based authoritative DNS servers after the system has joined their AD domain. To use this feature, a number of dyndns-specific sssd options have to be configured in sssd.conf. I spent close to a day of work finding out what made this mechanism work on one of our hosts, but not another - the root cause was determined to be that the host which had this feature working right away had the bind9-dnsutils package installed, which happens to provide `/usr/bin/nsupdate`. Even if this executable is not present, sssd will willingly let itself be configured with AD-based dyndns updates, but cannot actually perform them. The dyndns update mechanism repeatedly execv()s `nsupdate` if it was found during initialization at src/providers/be_dyndns.c:1188 as per the source package of sssd-ad 2.4.1 in bullseye. I therefore think it's a sound idea to have bind9-dnsutils in either Suggests or Recommends of the sssd-ad package, as an arguably significant portion of its functionality depends on it having been installed. Thanks for your consideration, and the great work on sssd in Debian!
Bug#756008: postgresql-common: pg_upgradecluster 9.3 - 9.4 fails
This exact problem, together with an undocumented and obscure
5-seconds-timeout in pg_upgradecluster's invocation of `pg_ctlcluster
stop`, nearly made me pull my hair out yesterday.
I successfully tested the planned upgrade from 9.0 to 9.4 in the staging
environment, but because the live database requires more than 5 seconds
to properly shutdown, pg_upgradecluster died very early with a
nondescript error message, costing me more than an hour hunting down
thesource of the problem while production was suffering a scheduled, yet
prolonged downtime. The following was its death note:
8
Stopping old cluster...
pg_ctl: server does not shut down
Error: Could not stop old cluster
8
After some frantic digging, I solved the problem by temporarily
monkey-patching /usr/bin/pg_upgradecluster to stop the old cluster like
presented below:
8
# stopping old cluster, so that we notice early when there are still
# connections
if ($info{'running'}) {
get_encoding $version, $cluster;
print Stopping old cluster...\n;
my @argv = ('pg_ctlcluster', $version, $cluster, 'stop', '-m',
'fast', '--');
push @argv, ('-t', '30') if $version = '8.4';
error Could not stop old cluster if system @argv;
}
8
I'm not sure what the reason for the (original; I changed it to 30 to
get it to work with our setup and workload) 5s timeout being there is
(and I don't think that trick with passing additional argv elements
after a double-dash down to pg_upgrade is documented anywhere?!); maybe
it should just get removed instead of relying on total guesswork about
how long it could take to stop a user's cluster (esp. in the default
smart mode, 5s seems VERY unlikely for busy servers).
Thanks very much for taking note of this problem, and trying to help fix it!
--
Mit freundlichen Grüßen
Johannes Truschnigg
Senior System Administrator
--
mailto:johannes.truschn...@geizhals.at (in dringenden Fällen bitte an
i...@geizhals.at)
Geizhals(R) - Preisvergleich Internet Services AG
Obere Donaustrasse 63/2
A-1020 Wien
Tel: +43 1 5811609/87
Fax: +43 1 5811609/55
http://geizhals.at = Preisvergleich für Österreich
http://geizhals.de = Preisvergleich für Deutschland
http://geizhals.eu = Preisvergleich EU-weit
Handelsgericht Wien | FN 197241K | Firmensitz Wien
Bug#759584: gearman-job-server: Gearman job server init script uses harcoded --listen argument
Hi, it is, in my opinion, absolutely unacceptable that the /etc/default/gearman-job-server configuration file has no effect on jessie installations that use systemd to manage services. The new service file proposed in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759584#10 apparently fixes the issue, so PLEASE commit the fix. I've also noticed that the package installs an upstart job configuration file. We're not using upstart, but I'd wager it might need the same treatment (if it's not better to just discontinue upstart support altogether for the package). Thanks for taking note of this issue, and its easy fix. -- Mit freundlichen Grüßen Johannes Truschnigg Senior System Administrator -- mailto:johannes.truschn...@geizhals.at (in dringenden Fällen bitte an i...@geizhals.at) Geizhals(R) - Preisvergleich Internet Services AG Obere Donaustrasse 63/2 A-1020 Wien Tel: +43 1 5811609/87 Fax: +43 1 5811609/55 http://geizhals.at = Preisvergleich für Österreich http://geizhals.de = Preisvergleich für Deutschland http://geizhals.eu = Preisvergleich EU-weit Handelsgericht Wien | FN 197241K | Firmensitz Wien -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693960: [Pkg-sysvinit-devel] Bug#693960: sysvinit: Undocumented, obscure limit for process field in inittab entries
On Thu, Nov 22, 2012 at 05:30:31PM -0200, Henrique de Moraes Holschuh wrote: Eh, should we also increase that limit to something larger [if it is feasible to do so] ? Whilst I do not like that kind of arbitrary limit, I don't think it's critically important (let alone good) to have absurdly long lines in inittab. If you need to do something that doesn't fit in 127 bytes on its command line, you might just as well write a wrapper, and call that fron inittab. Helps keeping things tidy - but that's personal preference of course. -- with best regards: - Johannes Truschnigg ( johan...@truschnigg.info ) www: http://johannes.truschnigg.info/ phone: +43 650 2 17 xmpp: johan...@truschnigg.info Please do not bother me with HTML-email or attachments. Thank you. signature.asc Description: Digital signature
Bug#693960: sysvinit: Undocumented, obscure limit for process field in inittab entries
Package: sysvinit
Version: 2.88dsf-13.1+squeeze1
Severity: minor
Tags: patch
I added a new entry to inittab on a busy host which did not seem to start upon
invoking `telinit q`. Syslog received the following message:
Nov 22 10:16:29 r7 init: /etc/inittab[93]: process field too long
This limit (127 characters) is not documented in man 5 inittab, nor anywhere
else I looked. In init's source file, there are error messages the explicitely
state length limits for other fields in inittab (which a user is much less
likely to overflow, I think), which seems kind of weird.
The attached patch adds the length limit information to init's error message
and to the appropriate man page.
-- System Information:
Debian Release: 6.0.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-0.bpo.3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages sysvinit depends on:
ii initscripts2.88dsf-13.1+squeeze1 scripts for initializing and shutt
ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib
ii libselinux12.0.96-1 SELinux runtime shared libraries
ii libsepol1 2.0.41-1 SELinux library for manipulating b
ii sysv-rc2.88dsf-13.1+squeeze1 System-V-like runlevel change mech
ii sysvinit-utils 2.88dsf-13.1+squeeze1 System-V-like utilities
sysvinit recommends no packages.
sysvinit suggests no packages.
-- no debconf information
diff -u -r a/sysvinit-2.88dsf/man/inittab.5 b/sysvinit-2.88dsf/man/inittab.5
--- a/sysvinit-2.88dsf/man/inittab.5 2009-09-10 10:28:49.0 +0200
+++ b/sysvinit-2.88dsf/man/inittab.5 2012-11-22 10:32:17.554426005 +0100
@@ -66,7 +66,7 @@
.B init
will not do utmp and wtmp accounting for that process. This is needed for
gettys that insist on doing their own utmp/wtmp housekeeping. This is also
-a historic bug.
+a historic bug. The length of this fiels is limited to 127 characters.
.\}}}
.PP
The \fIrunlevels\fP field may contain multiple characters for different
diff -u -r a/sysvinit-2.88dsf/src/init.c b/sysvinit-2.88dsf/src/init.c
--- a/sysvinit-2.88dsf/src/init.c 2010-04-13 11:48:54.0 +0200
+++ b/sysvinit-2.88dsf/src/init.c 2012-11-22 10:28:54.653475075 +0100
@@ -1314,7 +1314,7 @@
if (rlevel strlen(rlevel) 11)
strcpy(err, rlevel field too long (max 11 characters));
if (process strlen(process) 127)
- strcpy(err, process field too long);
+ strcpy(err, process field too long (max 127 characters));
if (action strlen(action) 32)
strcpy(err, action field too long);
if (err[0] != 0) {
Bug#693960: Typo in original patch
Of course I managed to get a typo not only into my report, but also into the
attached patch: fiels is supposed to read field. I've attached a corrected
version for your convenience - sorry for the noise.
diff -u -r a/sysvinit-2.88dsf/man/inittab.5 b/sysvinit-2.88dsf/man/inittab.5
--- a/sysvinit-2.88dsf/man/inittab.5 2009-09-10 10:28:49.0 +0200
+++ b/sysvinit-2.88dsf/man/inittab.5 2012-11-22 10:32:17.554426005 +0100
@@ -66,7 +66,7 @@
.B init
will not do utmp and wtmp accounting for that process. This is needed for
gettys that insist on doing their own utmp/wtmp housekeeping. This is also
-a historic bug.
+a historic bug. The length of this field is limited to 127 characters.
.\}}}
.PP
The \fIrunlevels\fP field may contain multiple characters for different
diff -u -r a/sysvinit-2.88dsf/src/init.c b/sysvinit-2.88dsf/src/init.c
--- a/sysvinit-2.88dsf/src/init.c 2010-04-13 11:48:54.0 +0200
+++ b/sysvinit-2.88dsf/src/init.c 2012-11-22 10:28:54.653475075 +0100
@@ -1314,7 +1314,7 @@
if (rlevel strlen(rlevel) 11)
strcpy(err, rlevel field too long (max 11 characters));
if (process strlen(process) 127)
- strcpy(err, process field too long);
+ strcpy(err, process field too long (max 127 characters));
if (action strlen(action) 32)
strcpy(err, action field too long);
if (err[0] != 0) {
signature.asc
Description: Digital signature
