Bug#501289: still relevant?

[Alexander Sosna]

Hello,

can you try to reproduce the bug with csync2 2.0+73d3293-2 and fresh
certificates?

If nobody can, I am going to close the report.



Best regards,
Alexander Sosna

Bug#492635: csync2: xinetd info: Line 1: protocol missing

[Alexander Sosna]

On Sun, 27 Jul 2008 22:29:50 +0200 Michael Prokop m...@grml.org wrote:
 When upgrading csync2 I noticed:
 
 - IMPORTANT INFORMATION FOR XINETD USERS --
 The following line will be added to your /etc/inetd.conf file:
 
 csync2\t\tstream\ttcp\tnowait\troot\t/usr/sbin/csync2\tcsync2 -i
 
 If you are indeed using xinetd, you will have to convert the
 above into /etc/xinetd.conf format, and add it manually. See
 /usr/share/doc/xinetd/README.Debian for more information.
 Suggested entry (automatically converted using itox):
 
 Line 1: protocol missing
 ---

I can not (competently) reproduce your bug.

If I write tabs as \t and pipe it to itox, I get your error:

% echo csync2\t\tstream\ttcp\tnowait\troot\t/usr/sbin/csync2\tcsync2
-i | itox
service csync2\t\tstream\ttcp\tnowait\troot\t
{
type= RPC
rpc_version = usr/sbin/csync2\tcsync2
socket_type = -i
Line 1: protocol missing



But if I cat the generated /etc/inetd.conf or the configuration string,
everything works fine fore me:

% cat /etc/inetd.conf | itox
service csync2
{
socket_type = stream
protocol= tcp
wait= no
user= root
server  = /usr/sbin/csync2
server_args = -i
}

% echo csync2 stream tcp nowait root /usr/sbin/csync2 csync2 -i  | itox
service csync2
{
socket_type = stream
protocol= tcp
wait= no
user= root
server  = /usr/sbin/csync2
server_args = -i
}


Convertig the configuration looks like:
% cat /etc/inetd.conf | itox   /etc/xinetd.d/csync2


Can we close this bug?





Best regards,
Alexander


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#710275: postgresql-9.1: Needs restart on libc upgrade

[Alexander Sosna]

I can reproduce the bug by installing wheezy, starting postgres and
upgrading libc6(2.13 to 2.19). After that peer authentication does not
longer work.

logfile says: local user with ID 110 does not exist

It looks like getpwuid() is broken after the libc6 upgrade.
In postgresql/src/backend/libpq/auth.c:1793 the function getpwuid(uid)
returns NULL and triggers the error message.


A really simple solution should be to add the following line to
eglibc/debian/libc.postinst:102.

check=$check postgresql-8.4 postgresql-9.1 postgresql-9.2 postgresql-9.3

This leads to a restart of postgres after an libc6 upgrade and fixes the
problem.
It should not be necessary for smaller changes and bug fixes. So it
would be ok to trigger a restart only by performing major upgrades.

Should restarting postgres be the default after any libc6 upgrade or is
there a better way? (I do not mind to restart it)


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org