Re: portsentry´s dirs and permissions

Hi, On Mon, Dec 06, 1999 at 05:44:50PM +, Julian Gilbey wrote: > On Mon, Dec 06, 1999 at 10:55:43AM +0100, Guido Guenther wrote: > > Hi, > > I´m still on that portsentry package and unsure about the proper directories > > and permissions for some files, any comment

portsentry´s dirs and permissions

Hi, I´m still on that portsentry package and unsure about the proper directories and permissions for some files, any comments greatly appreciated: - upstream sets the configuration files 600, I changed that to 644 - Currently I put all state-enigne & log-files into /var/lib/portsentry. To my unde

debconf & daemons

Hi, The tutorial of debconf reads: > Your postinst uses debconf and starts a daemon that doesn't close > all inherited file descriptors (all such daemons are buggy, > really). This makes debconf hang, because the debconf frontend > waits for the daemon to close the fd's before continuing. > Note >

Re: /usr/lib

On Thu, Oct 28, 1999 at 03:57:54PM +0300, [EMAIL PROTECTED] wrote: > /usr/share may not be even if /usr/sbin is, since it is > meant for stuff that can be shared for multiple machines > over network and can be mounted from another machine. See the point, but currently portsentry is started as late

Re: /usr/lib

On Wed, Oct 27, 1999 at 08:32:12PM +0200, Goswin Brederlow wrote: > Hmm, usr won´t be available during boot. /etc/init.d/ or /sbin/ would > be better. Also since they are just for root, they shouldn´t be in the > normal users path. the main binary(portsentry) itself resides in /usr/sbin..so if this

Re: /usr/lib

On Wed, Oct 27, 1999 at 04:53:04AM +, David Coe wrote: > /usr/lib/portsentry is indeed the right place, as long as the scripts > don't change other than at installation/upgrade time. Then I'll put them in there, thanks. > > Sorry for my confusion. Sorry for causing confusion...my posting was r

/usr/lib

Hi, I'm currently working an a package for portsentry. In order to handle dynamic ip's I wrote a couple of perl scripts which are called from several other scripts e.g. /etc/init.d/portsentry, /etc/ppp/ip-up.d/portsentry, postinst. I don't want to put them in /usr/sbin (where portsentry resides).

start-stop-daemon

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 -