On Fri, 10 Sep 1999 23:39:37 +0200, Josip Rodin <[EMAIL PROTECTED]> wrote:
>On Fri, Sep 10, 1999 at 09:33:42PM +, Zygo Blaxell wrote:
>> I've noticed that when I build a Debian package, I get a filename for
>> the arch-specific parts of the package named something like
>> "hello_1.3-14.3_i386.d
start-stop-daemon can use pid files to check for running instances rather than
killing all instances. If you can get portsentry to make a pid file, and
specifiy that files names, then what you have curently will work.
Hi,
I'm currently working on a debian package for portsentry. Portsentry can detect
portscans(including stealth scans). One can start two instances of the program,
one with the -tcp option and one with -udp. Currently I'm using something like:
...
DAEMON="/usr/sbin/portsentry"
start-stop-daemon -
On Fri, Sep 10, 1999 at 09:33:42PM +, Zygo Blaxell wrote:
> I've noticed that when I build a Debian package, I get a filename for
> the arch-specific parts of the package named something like
> "hello_1.3-14.3_i386.deb". However, in the Debian FTP archive, the
> same package is named "hello_1.
I've noticed that when I build a Debian package, I get a filename for
the arch-specific parts of the package named something like
"hello_1.3-14.3_i386.deb". However, in the Debian FTP archive, the
same package is named "hello_1.3-14.3.deb" (with no "_i386").
Why is this? Are package files normal
Hello,
I'm working on a program that collects information to be used by the sys
admin. I don't want the collected information to be world writable (even
though this wouldn't be a security hole), but I want the program to run
from user accounts (with write access to its data).
Obviously, I have to
There are many schools of thought on handling bugs like
these in Debian. There even has been some bug wars of
closing and reopening the same bug repeatedly, because of
these differences. So, there is no right answer, everybody
just Does The Right Thing and hopes it will be accepted.
That said, whe
Le Fri, Sep 10, 1999 at 12:54:23AM +0100, Frankie Fisher écrivait:
> Maybe you could downgrade it or something.
No please close it if :
- the bug submitter doesn't respond to your questions
- you can't duplicate the problem with the last version
- the bug is quite old
- nobody else complained abo
On Thu, Sep 09, 1999 at 08:12:19PM -0400, Ben Darnell wrote:
> But in this case, there is no evidence that the bug actually exists in
> this package. The bug can't be reproduced, and the submitter can't be
> reached for additional information. If the bug was in this package, it
You could possib
On Fri, Sep 10, 1999 at 12:54:23AM +0100, Frankie Fisher wrote:
> > >
> > > Can I just close this bug?
> > >
> >
> > Sure, someone can always re-open it.
>
> Not that I am an authority on the subject (or have ever even been in a
> position to close a bug as I'm not even a maintainer yet), but t
10 matches
Mail list logo
