Hi,
here is the updated one-pager and Dtrace scripts.
One pager:
- Moved utilities from /usr/memcached/bin to /usr/bin.
- Java API: stability raised from Volatile to Uncommitted
- Hard link from /usr/lib/memcached to /usr/lib/isaexec and executables
in /usr/lib/<32>/memcached and /usr/l
Danek Duvall wrote:
> On Thu, Feb 28, 2008 at 12:20:11AM +0100, Roy Lyseng wrote:
>
>>>> Another issue: it is probably too late to do something about this now,
>>>> but does there exist a "best practice" document on how to use the
>>>> /usr
Danek Duvall wrote:
>>> 2) Acceptance of the Drtace probes
>> A review request was sent to dtrace-discuss late yesterday. Can we give
>> it a 2-day "timeout" (unless there are significant comments)?
>
> Seems fair, but do make sure they know it's a short timeout.
Will do.
>
>> Another issue
but does there exist a "best practice" document on how to use the
/usr/lib/isaexec to pick a 32/64 bit executable based on architecture?
The policy document "Recommended Installation Locations for
Solaris-compatible Software Components" just refers isaexec(3C), which
Danek Duvall wrote:
> On Tue, Feb 26, 2008 at 07:57:37PM +0100, Roy Lyseng wrote:
>
>> Really difficult to say, actually, as this is entirely up to the
>> open-source community. However, the difference between Volatile and
>> Uncommitted seems rather subtle to me :)
&g
Danek Duvall wrote:
> On Tue, Feb 26, 2008 at 03:11:17PM +0100, Roy Lyseng wrote:
>
>> Java API: The commitment level for the Java API was classified as
>> Volatile in LSARC/2007/385. Based on recent discussions, I am open for
>> reclassifying this as Uncommitted, if
ate this. Setting up memcached to listen on a
loopback interface does not make sense, as it is always used in
machine-to-machine communication. Is there any other product that
actually do this?
BTW, I guess you really mean interface, and not port?
Thanks,
Roy
>
> On Feb 25, 2008, at
James Gates wrote:
> Can you answer the questions about the Java API & if the probes have
> been discussed with the community. Thanks.
>
>
> Original Message
> Subject: Re: LSARC/2008/126 memcached 1.2.5 to be included in OpenSolaris
> Date: Mon, 25 Feb 2008 16:55:05 -0500
>
Casper.Dik at Sun.COM wrote:
>>
>> Jyri Virkki wrote:
>>> Roy Lyseng wrote:
>>>>> Thanks. Does memcached issue a warning in the log if it starts
>>>>> listening on ports at risk?
>>>> No. Do you know a way to identify ports th
Jyri Virkki wrote:
> Roy Lyseng wrote:
>>> Thanks. Does memcached issue a warning in the log if it starts
>>> listening on ports at risk?
>> No. Do you know a way to identify ports that are at risk? I guess we
>> would need to communicate with firewalls
oyd
>
> On Feb 25, 2008, at 2:20 AM, Roy Lyseng wrote:
>
>> Hi Lloyd,
>>
>> it is indeed possible to configure memcached to listen to local
>> addresses only. If the administrator decides to configure memcached to
>> listen on a publicly available
Hi Lloyd,
it is indeed possible to configure memcached to listen to local
addresses only. If the administrator decides to configure memcached to
listen on a publicly available address, a security hole may be opened.
There was a substantial discussion on Memcached and security during the
first
12 matches
Mail list logo
