Package: slony1-bin
Version: 1.1.5-1
Severity: important
Tags: patch

/etc/init.d/slony1 fails to start slony:

[EMAIL PROTECTED]:/home/wayne$ /etc/init.d/slony1 start
Starting Slony-I daemon: wayne_production-su: . /lib/lsb/init-functions ; 
start_daemon -p /var/run/slony1/wayne_production.pid /usr/bin/slon -f 
/etc/slony1/wayne_production/slon.conf -p /var/run/slony1/wayne_production.pid 
>>/var/log/slony1/slon-wayne_production.log 2>&1 </dev/null &: No such file or 
directory
 failed!

It appears that the su now requires the "-c" argument that used to be
implied.  Adding "-c" to the script fixes everything (see attached
patch).

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages slony1-bin depends on:
ii  libc6                         2.3.6-7    GNU C Library: Shared libraries
ii  libpq4                        8.1.3-4    PostgreSQL C client library
ii  postgresql-common             50         manager for PostgreSQL database cl

Versions of packages slony1-bin recommends:
ii  ntp-server       1:4.2.0a+stable-2sarge1 Network Time Protocol: common serv
ii  postgresql-8.1-s 1.1.5-1                 replication system for PostgreSQL

-- no debconf information
diff -ur slony1-1.1.5.orig/debian/slony1-bin.slony1.init 
slony1-1.1.5/debian/slony1-bin.slony1.init
--- slony1-1.1.5.orig/debian/slony1-bin.slony1.init     2006-05-16 
12:01:41.000000000 -0700
+++ slony1-1.1.5/debian/slony1-bin.slony1.init  2006-05-17 11:34:08.000000000 
-0700
@@ -44,7 +44,7 @@
 }
 
 d_start() {
-       su - postgres ". /lib/lsb/init-functions ; start_daemon -p $(pidfile 
$1) $DAEMON -f $(conffile $1) -p $(pidfile $1) >>$(logfile $1) 2>&1 </dev/null 
&"
+       su - postgres -c ". /lib/lsb/init-functions ; start_daemon -p $(pidfile 
$1) $DAEMON -f $(conffile $1) -p $(pidfile $1) >>$(logfile $1) 2>&1 </dev/null 
&"
 }
 
 d_stop() {

Reply via email to