i am using memcachepp from http://sourceforge.net/projects/memcachepp/
, this also contain no api to check whether is client is alive/
dead :-)
On Aug 19, 2:46 pm, Henrik Schröder skro...@gmail.com wrote:
What do you mean with client? All clients are libraries that are used within
your
Amaravathi,
You could simply run a version or stats command against the server.
Regards,
Patrick
Amaravathi Yagati wrote:
i am using memcachepp from http://sourceforge.net/projects/memcachepp/
, this also contain no api to check whether is client is alive/
dead :-)
On Aug 19, 2:46 pm,
I am trying to find a way to check if the memcachedclient is still
alive or not but it seems to be there is no public api for me to do so.
Can someone clarify this?
Thanks.
Chad
I am trying to find a way to check if the memcachedclient is still
alive or not but it seems to be there is no public api for me to do
so. Can someone clarify this?
Thanks.
Chad
Chad wrote:
I am trying to find a way to check if the memcachedclient is still
alive or not but it seems to be there is no public api for me to do
so. Can someone clarify this?
Not really. You should be able to use system level tools (i.e. netstat
-a | grep 11211) to see connections in the
sto
On Wed, 18 Aug 2010, Chad wrote:
I am trying to find a way to check if the memcachedclient is still
alive or not but it seems to be there is no public api for me to do
so. Can someone clarify this?
Thanks.
Chad
dormando wrote:
sto
I'm pretty sure he sent it only once. I think this is a problem with
Google's SMTP and MTAs if I recall correctly. This happened on a
majordomo based list I am on, and it died down after a little bit. I
On Wed, 18 Aug 2010, Matt Ingenthron wrote:
dormando wrote:
sto
I'm pretty sure he sent it only once. I think this is a problem with Google's
SMTP and MTAs if I recall correctly. This happened on a majordomo based list
I
