On Wed, Nov 26, 2008 at 08:05:00AM +0100, Yves-Alexis Perez wrote:
> btw, in init-function, below pidofproc there's a comment:
> # start-stop-daemon uses the same algorithm as "pidofproc" above.
I think that's the proper way to go. Quoting the pidof manpage: "If the
system has a start-stop- daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've tested the above patch and it seems to solve the problem. It took me
a couple of times reading though /lib/lsb/init-functions to understand why
though (use of $specified is confusing).
Also this problem doesn't seem to show in all circumstan
On mar, 2008-11-25 at 18:07 +0100, Petter Reinholdtsen wrote:
>
> [Philipp Kern]
> > *argh* pidofproc returns the pid of the init script -> portmap does
> > not start at all -> rpc.statd and other NFS daemons do not start.
> > This affects lenny and severely breaks on-boot mounting of NFS
> > shar
On Tue, Nov 25, 2008 at 07:06:04PM +0100, Yves-Alexis Perez wrote:
> Hmhm yes that looks spurious. It's weird nobody noticed this before,
> because it should break in many situations…
It's possible that it does break here due to subshell usage. Maybe
adding `-o $$' to pidof calls would help to ca
On Tue, Nov 25, 2008 at 06:07:40PM +0100, Petter Reinholdtsen wrote:
> [Philipp Kern]
> > *argh* pidofproc returns the pid of the init script -> portmap does
> > not start at all -> rpc.statd and other NFS daemons do not start.
> > This affects lenny and severely breaks on-boot mounting of NFS
> >
[Philipp Kern]
> *argh* pidofproc returns the pid of the init script -> portmap does
> not start at all -> rpc.statd and other NFS daemons do not start.
> This affects lenny and severely breaks on-boot mounting of NFS
> shares.
Hm, is this the /lib/lsb/init-functions implementation of pidofproc?
I
Processing commands for [EMAIL PROTECTED]:
> reopen 448470
Bug#448470: Portmap does not start if a random user has a process named portmap
'reopen' may be inappropriate when a bug has been closed with a version;
you may need to use 'found' to remove fixed versions.
Bug reopened, originator not cha
reopen 448470
found 448470 6.0-8
thanks
On Tue, Nov 25, 2008 at 09:15:16AM +1100, Aníbal Monsalve Salazar wrote:
> On Mon, Nov 24, 2008 at 03:57:35PM +0100, [EMAIL PROTECTED] wrote:
> >I suspect this is still not fixed. On a freshly installed Lenny system
> >of mine,
> Maybe that's how I could rep
On Mon, Nov 24, 2008 at 03:57:35PM +0100, [EMAIL PROTECTED] wrote:
>I suspect this is still not fixed. On a freshly installed Lenny system
>of mine,
Maybe that's how I could reproduce this bug. I'll do a fresh lenny
install this coming weekend.
>portmap refuses to start stating "Already running"
I suspect this is still not fixed. On a freshly installed Lenny system
of mine, portmap refuses to start stating "Already running". Adding
debug output to the init script shows that $(pidofproc portmap) returns
the PID of the shell running the init script ($$).
pidofproc falls back to pidof when t
10 matches
Mail list logo
