Prev: Trying to get UTF-8 to work
Next: zfs snapshort says "dataset is busy". Any better solution than remounting file system ?
From: Chris Ridd on 4 Feb 2010 02:35
On 2010-02-04 06:57:21 +0000, David Kirkby said:

> On 3 Feb, 21:55, Chris Ridd <chrisr...(a)mac.com> wrote:
>> � � <exec_method type="method"
>> � � � � � � � � �name="stop"
>> � � � � � � � � �exec=":true"
>> � � � � � � � � �timeout_seconds="60"/>
>>
>> � � <property_group name="startd" type="framework">
>> � � � <propval name="duration" type="astring" value="transient"/>
>> � � </property_group>
>>
>> Verbose... but it seems to work. I'm a bit unsure about the stop method.
>
> There is currently no 'clean' stop method for this program, so it will
> just stop when the OS is no longer running.

The above is what my "always running" job does. It certainly seems to
do what I want.

>
>> But maybe you want a more normal service that just runs whatever your
>> script runs, and monitors it for crashes?
>
> That would be an extra luxury I must admit.

That would be a very much simpler manifest.

>
>> Is it easier to get -R/usr/sfw/lib passed the linker when linking stuff?
>
> -R is not a great option, as potentially someone might have other
> (newer) libraries in another place such /usr/local/openssl/lib. I

It is a bit risky to assume that any two versions of a library are
binary/link compatible and can be switched between by a user. OpenSSL
has historically been very bad about this.

> want to distribute this as a binary (though its open-source). So I
> don't really want to hard-code the path. I've specifically built this
> on the earliest Solaris release 10 (03/05).

I'm a bit surprised sage doesn't include its own copy of openssl :-)

--
Chris

From: Chris Ridd on 4 Feb 2010 10:35
On 2010-02-04 14:41:13 +0000, David Kirkby said:

> Sorry Chris, for some reason I did not address the other parts of your
> message. I have to use Google groups now, since my ISP has stopped
> suporting newsgroups. I find that more frustrating, and easy to miss
> things. Anyway ...

Ouch, googlegroups is painful. The service from news.individual.net is
very good, for something like €10 per year.

>
> On Feb 4, 7:35 am, Chris Ridd <chrisr...(a)mac.com> wrote:
>> On 2010-02-04 06:57:21 +0000, David Kirkby said:
>>
>>> -R is not a great option, as potentially someone might have other
>>> (newer) libraries in another place such /usr/local/openssl/lib.  I
>>
>> It is a bit risky to assume that any two versions of a library are
>> binary/link compatible and can be switched between by a user. OpenSSL
>> has historically been very bad about this.
>
> I thought that by specifically using the first release of Solaris
> (03/05), I would be safe. As far as I can see, Solaris 10 has not
> updated from 0.9.7 of OpenSSL - only bug fixes have been applied.

With OpenSSL the letter following the numbers forms part of the version.

OpenSSL's willingness/need to break binary compatibility may be the
reason that Sun has not updated the library in its entirety, and
instead just fixed bugs.

NB I haven't noticed if OpenSSL still frequently break binary
compatibility or not. The last time I saw this was a few years back.
--
Chris

From: Chris Ridd on 4 Feb 2010 12:38
On 2010-02-04 17:00:48 +0000, David Kirkby said:

> There is a long discusson about the issues here
>
> http://blogs.sun.com/janp/entry/on_openssl_versions_in_solaris

That's a useful page, thanks.

> One good thing on reading that, is that OpenSSL is actually quite an
> important part of Solaris. Which makes it easy to claim that we are
> not breaching the GPL by linking against it. I thought were were on
> dodgy ground with that one, but it appears not.

Great!

--
Chris

 | 
Pages: 1
Prev: Trying to get UTF-8 to work
Next: zfs snapshort says "dataset is busy". Any better solution than remounting file system ?