Will Trillich [EMAIL PROTECTED] writes:
problem: xinetd, after working just fine and dandy for weeks at
a time, gets dozens of unexpected signal (source unknown)
and gives up the ghost.
questions:
1) what's the best way (e.g. debian way) to monitor active
On Thu, Jul 01, 2004 at 02:31:44PM -0500, Will Trillich wrote:
| On Thu, Jul 01 at 05:59PM +0100, Thomas Adam wrote:
| --- Will Trillich [EMAIL PROTECTED] wrote:
| #!/bin/bash
| /etc/init.d/some-daemon-here restart
|
| Better to use 'invoke-rc.d' here:
|
| invoke-rc.d script
On Thu, Jul 01, 2004 at 02:46:06PM -0500, Will Trillich wrote:
| On Wed, Jun 30 at 06:25PM -0400, Derrick 'dman' Hudson wrote:
| On Wed, Jun 30, 2004 at 04:34:06PM -0500, Will Trillich wrote:
| | problem: xinetd, after working just fine and dandy for weeks at
| | a time, gets dozens of
On Wed, Jun 30, 2004 at 10:43:54PM -0500, Will Trillich wrote:
| On Wed, Jun 30 at 06:25PM -0400, Derrick 'dman' Hudson wrote:
| On Wed, Jun 30, 2004 at 04:34:06PM -0500, Will Trillich wrote:
| | problem: xinetd, after working just fine and dandy for weeks at
| | a time, gets dozens of
On Thu, Jul 01 at 10:55AM -0400, Derrick 'dman' Hudson wrote:
$ apt-cache policy restartd
restartd:
Installed: 0.1.a-3
Candidate: 0.1.a-3
Version Table:
*** 0.1.a-3 0
990 http://http.us.debian.org sarge/main Packages
80 http://http.us.debian.org sid/main Packages
On Wed, Jun 30 at 11:20PM -0500, Jacob S. wrote:
On Wed, 30 Jun 2004 22:43:54 -0500
Will Trillich [EMAIL PROTECTED] wrote:
at http://backports.org, i search for restartd and get
Sorry, no packages found.
At the risk of starting a flamewar about whether djb's tools
are a good way
On Thu, Jul 01 at 08:58AM +0800, John Summerfield wrote:
Mark Ferlatte wrote:
Will Trillich said on Wed, Jun 30, 2004 at 04:34:06PM -0500:
questions:
1) what's the best way (e.g. debian way) to monitor active
daemons and restart them when necessary? maybe some
utility
--- Will Trillich [EMAIL PROTECTED] wrote:
#!/bin/bash
/etc/init.d/some-daemon-here restart
Better to use 'invoke-rc.d' here:
invoke-rc.d script restart
which is effectively a start-some-thing and quick return...
or does it need to be the non-returning call to the daemon
Will Trillich said on Wed, Jun 30, 2004 at 10:38:51PM -0500:
On Wed, Jun 30 at 03:43PM -0700, Mark Ferlatte wrote:
Will Trillich said on Wed, Jun 30, 2004 at 04:34:06PM -0500:
questions:
1) what's the best way (e.g. debian way) to monitor active
daemons and restart them when
On Thu, Jul 01 at 05:59PM +0100, Thomas Adam wrote:
--- Will Trillich [EMAIL PROTECTED] wrote:
#!/bin/bash
/etc/init.d/some-daemon-here restart
Better to use 'invoke-rc.d' here:
invoke-rc.d script restart
for daemon-config-file-settings, i'm more comfortable specifying
the
On Wed, Jun 30 at 06:25PM -0400, Derrick 'dman' Hudson wrote:
On Wed, Jun 30, 2004 at 04:34:06PM -0500, Will Trillich wrote:
| problem: xinetd, after working just fine and dandy for weeks at
| a time, gets dozens of unexpected signal (source unknown)
| and gives up the ghost.
|
|
--- Will Trillich [EMAIL PROTECTED] wrote:
for daemon-config-file-settings, i'm more comfortable specifying
the whole path. less chance of intervention or misdirection
based on $PATH mungings...
/etc/init.d is not in $PATH, and as such scripts are run as root anyway,
invoke-rc.d is perfect
On Thu, Jul 01 at 09:31PM +0100, Thomas Adam wrote:
--- Will Trillich [EMAIL PROTECTED] wrote:
for daemon-config-file-settings, i'm more comfortable
specifying the whole path. less chance of intervention or
misdirection based on $PATH mungings...
/etc/init.d is not in $PATH, and as such
--- Will Trillich [EMAIL PROTECTED] wrote:
starts with a slash, it's an absolute reference, no
uncertainties about it; if it does NOT start with a slash, then
your environmental variable $PATH is called upon to supply
likely directories to scan, looking for an executable by the
name you
problem: xinetd, after working just fine and dandy for weeks at
a time, gets dozens of unexpected signal (source unknown)
and gives up the ghost.
questions:
1) what's the best way (e.g. debian way) to monitor active
daemons and restart them when necessary? maybe
On Wed, Jun 30, 2004 at 04:34:06PM -0500, Will Trillich wrote:
| problem: xinetd, after working just fine and dandy for weeks at
| a time, gets dozens of unexpected signal (source unknown)
| and gives up the ghost.
|
| questions:
| 1) what's the best way (e.g. debian way) to
Will Trillich said on Wed, Jun 30, 2004 at 04:34:06PM -0500:
questions:
1) what's the best way (e.g. debian way) to monitor active
daemons and restart them when necessary? maybe some
utility already exists for this? or /proc/something?
or `ps ax`?
monit can
Mark Ferlatte wrote:
Will Trillich said on Wed, Jun 30, 2004 at 04:34:06PM -0500:
questions:
1) what's the best way (e.g. debian way) to monitor active
daemons and restart them when necessary? maybe some
utility already exists for this? or /proc/something?
or `ps ax`?
monit
On Wed, Jun 30 at 03:43PM -0700, Mark Ferlatte wrote:
Will Trillich said on Wed, Jun 30, 2004 at 04:34:06PM -0500:
questions:
1) what's the best way (e.g. debian way) to monitor active
daemons and restart them when necessary? maybe some
utility already exists for this?
On Wed, Jun 30 at 06:25PM -0400, Derrick 'dman' Hudson wrote:
On Wed, Jun 30, 2004 at 04:34:06PM -0500, Will Trillich wrote:
| problem: xinetd, after working just fine and dandy for weeks at
| a time, gets dozens of unexpected signal (source unknown)
| and gives up the ghost.
|
|
On Wed, 30 Jun 2004 22:43:54 -0500
Will Trillich [EMAIL PROTECTED] wrote:
On Wed, Jun 30 at 06:25PM -0400, Derrick 'dman' Hudson wrote:
On Wed, Jun 30, 2004 at 04:34:06PM -0500, Will Trillich wrote:
| problem: xinetd, after working just fine and dandy for weeks at
| a time, gets dozens
21 matches
Mail list logo
