Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <002301c2ba39$3cbc97d0$0201a8c0@sos>
From: "Sergey Okhapkin" <sos AT sokhapkin DOT dyndns DOT org>
To: "Alex Tribble" <alext96 AT softhome DOT net>, <cygwin AT cygwin DOT com>
References: <000001c2ba15$d7c4be70$0300a8c0 AT tribblesoft2>
Subject: Re: SysVInit: No symbolic link for /sbin/pidof
Date: Sun, 12 Jan 2003 07:50:50 -0500
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

Thanx! I will fix the packaging problem soon.

Sergey Okhapkin
Somerset, NJ
----- Original Message -----
From: "Alex Tribble" <alext96 AT softhome DOT net>
To: <cygwin AT cygwin DOT com>
Sent: Sunday, January 12, 2003 3:37 AM
Subject: SysVInit: No symbolic link for /sbin/pidof


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> The Cygwin SysVInit package include the pidof(8) manpage, but no such
> command exists. /sbin/pidof should be a symbolic link to
> /sbin/killall5
>
> Alex
>
> -----BEGIN PGP SIGNATURE-----
> Version: PGP 8.0 - not licensed for commercial use: www.pgp.com
>
> iQA/AwUBPiEpPG4IsMyAUEajEQIguACeKl9JsaXZvXIXySR4jj9CKijIIakAoO+M
> Peu5PzqVor0D8zPofRvDMkw9
> =Yjbh
> -----END PGP SIGNATURE-----
>
>
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
>



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/