Earlier today while I was making some changes to my NAT rules (I was
testing to see how many connection states I can track as a result of
the DDoS/syn flood I am currently under[1]) and it seems that
/etc/ping_hosts.sh got stuck in an infinite loop. I'm guessing it's
forking processes which are imm
On Tue, 6 May 2008 00:43:15 -0700, "David Rees" <[EMAIL PROTECTED]> wrote:
> Earlier today while I was making some changes to my NAT rules (I was
> testing to see how many connection states I can track as a result of
> the DDoS/syn flood I am currently under[1]) and it seems that
> /etc/ping_host
On Tue, May 6, 2008 at 6:12 AM, <[EMAIL PROTECTED]> wrote:
>
Was it just me, or did [EMAIL PROTECTED]'s reply look empty?
-Dave
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
David Rees wrote:
On Tue, May 6, 2008 at 6:12 AM, <[EMAIL PROTECTED]> wrote:
Was it just me, or did [EMAIL PROTECTED]'s reply look empty?
It was.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands,
On Tue, May 6, 2008 at 9:27 AM, Chris Buechler <[EMAIL PROTECTED]> wrote:
> David Rees wrote:
> > Was it just me, or did [EMAIL PROTECTED]'s reply look empty?
>
> It was.
Thought so. ;-)
Anyone have any ideas on the ping_hosts.sh getting stuck and
apparently looping? It's still doing it 8 hours
David Rees wrote:
On Tue, May 6, 2008 at 9:27 AM, Chris Buechler <[EMAIL PROTECTED]> wrote:
David Rees wrote:
Was it just me, or did [EMAIL PROTECTED]'s reply look empty?
It was.
Thought so. ;-)
Anyone have any ideas on the ping_hosts.sh getting stuck and
apparently loo
On 5/6/08, David Rees <[EMAIL PROTECTED]> wrote:
> Thought so. ;-)
>
> Anyone have any ideas on the ping_hosts.sh getting stuck and
> apparently looping? It's still doing it 8 hours later - I'd like to
> kill the process to let the box rest a bit, but if someone has any
> requests for informati
On Tue, May 6, 2008 at 10:06 AM, Scott Ullrich <[EMAIL PROTECTED]> wrote:
> Show the process information (ps awux | grep ping). It is normal for
> this process to be running quite a bit but I am not sure about 8
> hours.
root 59637 5.7 0.5 1744 1216 ?? S 7:51PM 58:41.28 /bin/sh
/
On 5/6/08, David Rees <[EMAIL PROTECTED]> wrote:
> root 59637 5.7 0.5 1744 1216 ?? S 7:51PM 58:41.28 /bin/sh
> /etc/ping_hosts.sh
> root1510 0.0 0.3 1268 732 ?? Is2:06PM 0:00.04
> minicron 240 /var/run/ping_hosts.pid /etc/ping_hosts.sh
> root 59636 0.0 0.5 171
On Tue, May 6, 2008 at 11:31 AM, Scott Ullrich <[EMAIL PROTECTED]> wrote:
> Since you appear to have some shell script knowledge check the script
> where it reads in a couple of files. Can you take a look at the
> files that it reads in and tell me how many entries in the file there
> are?
>
On 5/6/08, David Rees <[EMAIL PROTECTED]> wrote:
> All the files appear to be empty. No files are large. I suspect that
> whatever triggered the issue has since resolved itself, otherwise we'd
> have ping_hosts.sh scripts piling up every 5 minutes.
>
> My best guess is that it's somehow gotten s
On Tue, May 6, 2008 at 12:09 PM, Scott Ullrich <[EMAIL PROTECTED]> wrote:
> On 5/6/08, David Rees <[EMAIL PROTECTED]> wrote:
> > If my theory is correct, I would suggest two fixes:
> >
> > 1. Make sure the config file is written atomically to the filesystem.
> > This means writing the file t
On 5/6/08, David Rees <[EMAIL PROTECTED]> wrote:
> I did some checking in the PHP code - it does look like there are
> various locations where the /conf/config.xml or
> {$g['conf_path']}/config.xml or /cf/conf/config.xml are written just
> using a plain fopen, write, close. This does leave you o
On Tue, May 6, 2008 at 1:54 PM, Scott Ullrich <[EMAIL PROTECTED]> wrote:
> On 5/6/08, David Rees <[EMAIL PROTECTED]> wrote:
> > I did some checking in the PHP code - it does look like there are
> > various locations where the /conf/config.xml or
> > {$g['conf_path']}/config.xml or /cf/conf/conf
On Tue, May 6, 2008 at 2:07 PM, David Rees <[EMAIL PROTECTED]> wrote:
> Ah, missed that. I did see a few other places where it appears that
> config.xml is written besides through the write_config routine...
> Modifying write_config to update the config file atomically will be
> straight forwar
On Tue, May 6, 2008 at 5:30 PM, David Rees <[EMAIL PROTECTED]> wrote:
>
> OK, attached is a patch to /etc/config.inc that makes sure that the
> config.xml and config.cache is updated atomically. The patch adds a
> function function "write_safe_file" with 3 arguments: $file, $content,
> $force_b
On Tue, May 6, 2008 at 5:30 PM, David Rees <[EMAIL PROTECTED]> wrote:
> OK, attached is a patch to /etc/config.inc that makes sure that the
> config.xml and config.cache is updated atomically. The patch adds a
> function function "write_safe_file" with 3 arguments: $file, $content,
> $force_binary.
17 matches
Mail list logo
