Tag Archives: OPTIONS

Linux

Version of OpenSSL being used

Leave a comment

By CHoggarth

Hello

I’m relatively new to technologies like Apache & ssl but have some years
experience with Unix. My question concerns the version of OpenSSL which is
genuinely being used on our server & how is that set.

The server is running Solaris 10. I’ll show output from various commands:

Code:
:/usr/local/ssl # pkginfo -l SMCossl
PKGINST: SMCossl
NAME: openssl
CATEGORY: application
ARCH: sparc
VERSION: 1.0.1c
BASEDIR: /usr/local
VENDOR: The OpenSSL Group
PSTAMP: Steve Christensen
INSTDATE: Aug 17 2012 07:27
EMAIL: steve@smc.vnet.net
STATUS: completely installed
FILES: 1871 installed pathnames
1 shared pathnames
43 directories
32 executables
30745 blocks used (approx)

:/usr/local/ssl #

Code:
:/usr/local/ssl # openssl version -a
OpenSSL 1.0.1c 10 May 2012
built on: Sun May 13 18:44:13 EDT 2012
platform: solaris-sparcv9-gcc
options: bn(64,32) rc4(ptr,char) des(idx,cisc,16,long) idea(int) blowfish(ptr)
compiler: gcc -fPIC -DOPENSSL_PIC -DOPENSSL_THREADS -D_REENTRANT -
DDSO_DLFCN -DHAVE_DLFCN_H -m32 -mcpu=ultrasparc -O3 -fomit-frame-
pointer -Wall -DB_ENDIAN -DBN_DIV2W -DOPENSSL_BN_ASM_MONT -DSHA1
_ASM -DSHA256_ASM -DSHA512_ASM -DAES_ASM -DGHASH_ASM
OPENSSLDIR: "/usr/local/ssl"
:/usr/local/ssl #

But if I run telnet xxx.xxx.xxx.xxx 80 & OPTIONS / HTTP1.0 from our network it reports 0.9.8x:

Code:
HTTP/1.1 200 OK
Date: Tue, 19 Feb 2013 10:20:37 GMT
Server: Apache/2.2.23 (Unix) mod_ssl/2.2.22 OpenSSL/0.9.8x DAV/2
Allow: POST,OPTIONS,GET,HEAD
Vary: Accept-Encoding
Content-Length: 0
Connection: close
Content-Type: text/html

Connection to host lost.

W:>

I’ve been advised to use OPTIONS / HTTP1.0 to determine which version is genuinely being used.

We have in the past installed SSL by package (the most recent being 1.0.1) & source (presumably the most recent being 0.9.8x).

I need to upgrade SSL on this server & I would like to use the 1.0.1 stream (I understand packages are more likely to be available for this & that’s certainly easier to install). But I can’t figure out why the system is really using 0.9.8x when the server itself is saying that 1.0.1 is being used.

I am assuming that the OPTIONS / HTTP1.0 command is giving me the true version.

Can anyone clarify what might be happening & advise how I can start using 1.0.1?

Thanks, Chris

…read more
Source: FULL ARTICLE at The UNIX and Linux Forums

Linux

Boinc Monitor 2.0 (Plasmoid Script)

Leave a comment

ThumbnailBoinc Monitor 2.0
(Plasmoid Script)
Boinc Monitor is a plasmoid written in python that allows you to monitor the activities of BOINC directly on your desktop. It shows the progress work by each individual core of your PC with reference to the ram used by the process, the percentage of the work done and the time elapsed. Also shows the numbers of workunits in pending, cached and finished, and the last few lines of the BOINC log.

OPTIONS:
BOINC folder path – The path of BOINC working folder. Default: /var/lib/boinc-client/
BOINC user name – The name of your BOINC user. Default: boinc
Preferred project – Your favorite project to display (name, credits, team). Default: None.
Update interval – The refresh interval of the plasmoid. Default: 1 minute.
Log line numbers – The number of log line to show. Default: 5 lines.
Cut Log line after – The number of characters after which the line of the log is cut. Default: 95 chars.
Cpu load limit – The minimum rate of the CPU workload to show the workunit. Default: 20%.
[S/R] wait timeout – The waiting time after a suspend/resume call. Default: 5 seconds.

IMPORTANT:
For a perfect view of the plasmoid the system must have the “Verdana” font installed.

INSTRUCTIONS:
To get plasmoid that works well is necessary to copy the file boinc-monitor from the docs folder to the folder /etc/sudoers.d/ (need root privileges).

If your BOINC user is not “boinc”, please edit the file and replace it with your BOINC username.

Remember that the boinc-monitor file must be in mode 0440 (sudo chmod 0440 boinc-monitor).

Pay attention if in your /etc/sudoers there is the line – #includedir /etc/sudoers.d – otherwise the file boinc-monitor cannot be parsed. Thanks to Thomas Gorzka for his time!

AVAILABLE LANGUAGES:
English
Italian
German (thanks to Thomas Gorzka)

Who wants adding a translation, in the docs folder there is the file boinc-monitor.pot. Complete the translation (msgstr “translation goes here”) and send the file to m4x1m@inwind.it

–

That’s all!

If you like this plasmoid please leave a comment!

changelog:
v2.0:
– Auto Expand “Elapsed” field to print a result that show more than 24 hours.

v1.9:
– Added option to set timeout wait after a suspend/resume call (a too low value might not give time to PC to remove/create the process ids).
– Show more informations when resuming a workunit.
– Fixed minor bugs.

v1.8:
– Added the ability to suspend/resume process.
– Fixed an issue at the initialization of the script.
– Fixed minor bugs.

v1.7:
– Added multilanguage locale.
– Added an extra check to the file boinc-monitor in /etc/sudoers.d/

v1.6:
– Added a second command to check if BOINC is running (this is a workaround for systemd, thanks to Thomas Gorzka).
– Fixed minor bugs.

v1.5:
– No more write the options in a an external file, but use the internal system of plasma for read/write the configuration.

v1.4:
– Perfected the method of recognition of the BOINC user.
– Fixed minor bugs.
– Fixed minor graphics bugs.

v1.3:
– Fixed issue related at initialize of plasmoid for not packaging version of BOINC.
– Fixed issue related the choose of preferred project.
– Fixed minor bugs introduced with the previously version.

v1.2:
– Fixed bug related the preferred project chosen that no longer exists.
– Fixed little bug if the user choose a project that is not in any team.
– Added more controls to prevent errors.

v1.1:
– Changed the way to get the slot used by process (see README.txt in docs folder).
– Added PID column to the working list.
– Fixed minor graphics bugs.

v1.0:
– First script release.

[read more]

job recommendations:

Sales Engineer full time employee
ownCloud Inc. United States of America, Boston more about this offer

[more jobs]

Source: FULL ARTICLE at KDE Apps

Linux

GNU-Screen Stuff problems

Leave a comment

Code:
OPTIONS=”java -Xms1024M -Xmx1024M -jar craftbukkit.jar”
PROCESS=server01

screen -dmS $PROCESS $OPTIONS nogui # Starting the application
screen -x $PROCESS -X stuff `printf “stopr”` # Closing the application
screen -x $PROCESS # Attaching to the terminal of the application
The problem I’m facing with is that “-X stuff `printf “stopr”`” Doesn’t work if the process has never been “screen -x $PROCESS” (attached to the screen and then Ctr-A-D)

So is there a way to make “stuff” work without that the screen has to be attached once?
Source: The UNIX and Linux Forums