Hi,
I don't know who at Mantech was a subscriber to SLUG, it could be one of
the following
Adam Buck
Guy Shute
Jamie Powell
If it is any of these guys, could you please remove their
@mantechit.com.au address from your list?
I am currently getting their mail forwarded and would prefer not to have
it filled up with SLUG announcements. I cannot unsubscribe as I have no
idea what their password is/was.
Please help
Thanks
Kind Regards,
Stephen Winnick
Mantech International Systems Recruitment
Level 4
221 Miller St
North Sydney
NSW 2060
ph:02 9957 1022
fax:02 99571329
-----Original Message-----
From: [email protected] [mailto:[email protected]] On
Behalf Of dave b
Sent: Tuesday, 21 December 2010 1:19 PM
To: Jam
Cc: [email protected]
Subject: Re: [SLUG] Debian/Ubuntu way of having multiple memcached
daemon's
On 21 December 2010 13:04, Jam <[email protected]> wrote:
> On Tuesday 21 December 2010 09:00:04 [email protected] wrote:
>> Using apt-get, you can automagically install memcached. It's great as
>> it starts a daemon and that daemon will start on boot.
>>
>> Though for Christmas I need two daemons running on different ports:
>> 11211 and 11212.
>>
>> I've duplicated the following files and tweaked them, so a second
>> daemon can start.
>>
>> /etc/init.d/memcached -> /etc/init.d/memcached_11212
>> /etc/memcached.conf -> /etc/memcached_11212.conf
>> /usr/share/memcached/scripts/start-memcached ->
>> /usr/local/share/memcached/scripts/start-memcached
>>
>> Using update-rc.d the above daemon starts on boot as well (great).
>>
>> Now if memcached has a security update, apt-get will restart the
>> original packaged daemon, not my second instance. How can I make my
>> second instance upgrade friendly?
>>
>> Disclaimer: My new found obsession is upgrade friendliness, so my
>> intentions are not strictly memcached related, but it's the simplest
>> example I can think of.
>
> Simon, utter respect, but this sounds like UADUFMBS (Unadulterated
Unmitigated
> ..) The normal way (even with upstart) it to put the daemon start
script in
> /etc/init.d [There are skeleton and example files]
>
> Then you can do the distro equivalent of rcmyapp start/stop/restart
etc.
> I like SuSE's rc[app] paradigsm, so I do
> ln -s /etc/init.d/myapp /usr/sbin/rcmyapp
> but that is just detail. Whatever works for you.
>
> In any even, doing it the standard way means no worry about upgrade
etc and it
> complies with KISS (keep it simple ..)
>
Well that seems ok - at least to me.
He would just need to ensure that the lock and or run files are kept
separate.
--
The better part of valor is discretion. -- William Shakespeare,
"Henry IV"
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
