IL PROTECTED]>; "modperl list" <[EMAIL PROTECTED]>
Sent: Wednesday, April 17, 2002 9:08 PM
Subject: Re: Sharing Variable Across Apache Children
> You had us going for a whileI thought you are talking about some
> distributed
> session management (accross different bo
- Original Message -
From: "Medi Montaseri" <[EMAIL PROTECTED]>
To: "Andrew Ho" <[EMAIL PROTECTED]>
Cc: "Benjamin Elbirt" <[EMAIL PROTECTED]>; "modperl list" <[EMAIL PROTECTED]>
Sent: Wednesday, April 17, 2002 9:08 PM
Subject: Re: Sha
Stas Bekman wrote:
> Medi Montaseri wrote:
>
>> Unfortunately everyone wants to use email for everything.the
>> proper way would
>> be to use some facilities that have proven track record, like
>> syslogd(1d) on each
>> box.
>
>
> syslog(3) is not a very scalable solution because it's sl
Medi Montaseri wrote:
> Unfortunately everyone wants to use email for everything.the proper
> way would
> be to use some facilities that have proven track record, like
> syslogd(1d) on each
> box.
syslog(3) is not a very scalable solution because it's slow.
It's also unreliable because it
> Abstracting access to data is only half of the storythe more
challenging
> part is race conditions and lock management...
All of the data sharing tools take the logistics of multi-process
read/write situations into account, although they do it in different
ways. Some use file locking, othe
Unfortunately everyone wants to use email for everything.the proper
way would
be to use some facilities that have proven track record, like syslogd(1d)
on each
box. As you know syslogd() allows you to route a message to a remote
box. So,
you assign one of your boxes as the final or central po
You had us going for a whileI thought you are talking about some
distributed
session management (accross different boxes)
Another suggestion is to use lbnamed. lbnamed is a DNS server and Load
Balancing
server that listens to port 53 and resolves IPs, but on the other side of its
personal
Abstracting access to data is only half of the storythe more challenging
part is race conditions and lock management...
Perrin Harkins wrote:
> Stas Bekman wrote:
> > You cannot do that unless you use IPC, which is usually only useful if
> > he variable is small. DBM file is another solution
[EMAIL PROTECTED]; modperl list
: Subject: Re: Sharing Variable Across Apache Children
:
:
: On Wed, 17 Apr 2002, Perrin Harkins wrote:
:
: > Benjamin Elbirt wrote:
: > > Well, lets assume that I were to go with
: > > the shared memory option anyway..
On Wed, 17 Apr 2002, Perrin Harkins wrote:
> Benjamin Elbirt wrote:
> > Well, lets assume that I were to go with
> > the shared memory option anyway... what would the pitfalls be / concerns?
>
> As mentioned before, you'd probably be better off with MLDBM::Sync or
> Cache::Cache. You can try IPC
Benjamin Elbirt wrote:
> Well, lets assume that I were to go with
> the shared memory option anyway... what would the pitfalls be / concerns?
As mentioned before, you'd probably be better off with MLDBM::Sync or
Cache::Cache. You can try IPC::Shareable, but a lot of people seem to
have trouble
Is the webserver useful if you have an error that warrants sending a
mail? If sending an email means the server is broken having a flood of
mails may be a feature. It will be incentive to fix whatever is
breaking your server/db.
Also, I would strongly recommend keeping your warning system as simpl
Benjamin Elbirt wrote:
> Hey,
>
> I've gotten it so that I can define a variable across apache children,
> however when I update the variable, it only updates for the active
> child. Is there any way to share a variable across children so no
> matter what child is doing the update, the variable
13 matches
Mail list logo
