Sometimes you want to debug a service with a clear text protocol, but it uses unix sockets instead of INET sockets.
Surprisingly, there is little info on this around the net.
An easy solution would be socat:
socat UNIX-CONNECT:/var/run/blabla/nameofthe.sock STDIN
EDIT: Linux consultant Stefan Seyfried pointed out, that from openSUSE 12.1 onwards you can also use netcat. The new opensuse version ships netcat-openbsd.
The syntax is:
nc -U /var/run/blabla/namedersocket.sock
Today, openSUSE Program Manager Andreas Jaeger announced that openSUSE will stop shipping Sun Java in the upcoming 12.1 release.
Distribution users will now only be offered the GPLed openJDK. In a recent announcement, Oracle declared openJDK to be the new official reference implementation for Java SE7. Along with that move, Oracle dropped the “Distributor’s License for Java (DLJ)” which was required for redistributing Sun Java. Users depending on Sun/Oracle Java are now required to download it directly from the oracle website. Since the acquisition of sun by oracle, the companny has been known for questionable moves which alienate parts of the opensource community. Among these was the OpenOffice dispute which led to the departure of many developers to form LibreOffice. The former sun-owned mysql database has also seen a fork called MariaDB. According to Jaeger, openSUSE will continue to provide the existing packages in the Java:sun:Factory project but will not update them anymore and won’t ship them with the new distribution. Users are urged to switch to either openJDK or the versions available directly from Oracle.
Gerard Xavier Marcel Dipardieu?:
Der französische Klaus Kinski pinkelt in ein Flugzeug, sagt die Süddeutsche.
Oh mon dieu! Gerard Dipardieu hat drei Kinder gemacht, sagt man. Das hat er mir voraus.
Jennifer Lynn Lopez?
Sie legt nach, sagt lieblingsstar.com
Tierschützer kritisieren sie, weil sie gern Pelze trägt. Mir ist das nicht so wichtig! Sie war ist zum dritten Mal verheiratet. Das hat sie mir voraus.
Dan Aykroid?
Er wird in einer Open-Air-Vorführung in Überlingen gezeigt. Maximal 500 zuschauer sehen einen der wahrscheinlich unterschätztesten Schauspielern des US-Kinos sich nochmal im “Blues Brother”-Film unter freiem Himmel an. Ich finde es schade, dass es so ist!
Ralf Lang?
- arbeitet an einer PHP-Applikation
- hat die openSUSE-Horde-Pakete auf den aktuellen Stand gebracht
- hat für Horde 4 in einem experimentellen Pfad das Sperren von Benutzern (dauerhaft oder auf Zeit) und das Reagieren auf zuviele gescheiterte Logins implementiert. Ob diese Features in dieser Form in den Mainstream-Zweig kommen, ist noch nicht entschieden. Das Interface lehnt sich an an das Interface des Block-Login-Features des Kolab-Treibers an und sollte alte Settings aus Horde 3 übernehmen. Allerdings ist die Implementierung jetzt treiberunabhängig und funktioniert z.B. auch mit LDAP, passwd, shibboleth oder anderen weniger gewöhnlichen Treibern. Dabei habe ich viel dazugelernt und nicht alles gleich richtig gemacht.
B1 Systems GmbH?
Eine der größten konzernfreien deutschen Opensource-Consulting, Training und Support-Firmen mischt kräftig mit bei openStack, einer führenden Cloud-Lösung.
Jan Schneider just posted a damn cool use case for the Horde_Service_Twitter library. Using this library, just a few lines of php code are enough to send messages to your twitter stream like this:
#!/usr/bin/env php
<!--?php
/* Keys - these are obtained when registering for the service */
$keys = array(
'consumer_key' => '',
'consumer_secret' => '',
'access_token' => '',
'access_token_secret' => ''
);
/* Enable autoloading. */
require 'Horde/Autoloader/Default.php';
/* Create the Twitter client */
$twitter = Horde_Service_Twitter::create(array('oauth' => $keys));
/* Send tweet */
try {
$twitter->statuses->update($argv[1]);
} catch (Horde_Service_Twitter_Exception $e) {
$error = Horde_Serialize::unserialize($e->getMessage(), Horde_Serialize::JSON);
echo "$error->error\n";
exit(1);
}
Now that’s neat, isn’t it.
In another team I worked with, we used a perl library which sent jabber/xmpp streams to our chat accounts when something ran into an uncought exception.
This might be worth porting to PHP/Horde some day.
Traditionally, Horde only knows two kinds of users: Users with administration flag and users without. The list of admins is a static entry in the horde config file. It’s all or nothing – either a user gets access to all admin functions or to none. At least until recently.
Last October I wrote about a patch for Horde 3 which allows permission-based access to individual admin privileges. This patch has now been ported to Horde 4 and is incorporated in Horde 4.0.6. You can now assign a user the task of managing groups without allowing him to use the permissions admin and grant himself additional privileges. Or you can delegate emergency password resets to a group of trusted people without confusing them with icons like the PHP Shell. Only those admin functions are shown which the user has access to. Another side effect: Even if a user has all admin permissions, he is still not recognised as an admin and won’t be shown things that admins always have to see regardless of their permissions and settings.
In theory, you can now give yourself all admin permissions and safely delete yourself out of the admin list – as long as you have the “configuration” permission, you can always go back and restore without manually editing the conf.php file.
The Administration permissions are handled in the permissions screen just like any other user permissions. They live under the “horde” component. Currently only the “show” flag is actually recognized but this will be expanded later.
There have been some migrations of Horde 3 to Horde 4 recently – not all went smooth from the start.
Some top issues of messing things up and how to avoid it:
To get around this you should
Today the openSUSE project announced that their packaging solution OpenSUSE Build Service will be re-branded to highlight the crossplatform nature of the product. The new name of the platform will be Open Build Service (OBS). Commercial support will also be available soon.
Ralph Dehner, CEO at B1 Systems GmbH noted:
“In the past B1 Systems has written build environments for the customers by itself. With the open Build Service now exists a “standard” which makes it easy to build packages for different distributions and architectures.
This will be also interesting for many other open source projects.”
Today I submit-requested the Horde 4 Application Framework and the stable apps for openSUSE Factory.
This is becoming openSUSE 12.1 if the packages get accepted on time. They are currently in review.
openSUSE Legal team wants to review all packages’ licensing – I’m sure that’s NOT the fun part of their job.
If everything works fine, openSUSE 12.1 will be the first distribution to feature horde 4 in their mainstream repositories.
The %php_pear_gen_filelist macro, maintained by Christian Wittmer, is really handy for packaging php pear software packages. It generates rpmlint-happy filelists and if you manage to get the dependencies right, packaging pear stuff for rpm is really a no-brainer. But the standard recipe for using this macro has one drawback: It’s ignorant of installed 3rd party roles and channels. 3rd party pear packages which depend on their channel being registered normally fail.
The workaround is easy: Copy the channel file to the build location.
Example:
#
# spec file for package php5-pear-Horde_Auth (Version 1.0.3)
#
# Copyright (c) 2011 Ralf Lang.
#
# All modifications and additions to the file contributed by third parties
# remain the property of their copyright owners, unless otherwise agreed
# upon. The license for this file, and modifications and additions to the
# file, is the same license as for the pristine package itself (unless the
# license for the pristine package is not an Open Source License, in which
# case the license is the MIT License). An “Open Source License” is a
# license that conforms to the Open Source Definition (Version 1.9)
# published by the Open Source Initiative
# Please submit bugfixes or comments via http://bugs.opensuse.org/# norootforbuild
Name: php5-pear-Horde_Auth
%define pear_name Horde_Auth
%define pear_sname horde_auth
Summary: PEAR: Horde Authentication API
Version: 1.0.3
Release: 1
License: LGPL
Group: Development/Libraries/PHP
Source0: http://pear.horde.org/get/Horde_Auth-%{version}.tgz
BuildRoot: %{_tmppath}/%{name}-%{version}-root-%(%{__id_u} -n)
URL: http://pear.horde.org/package/Horde_Auth
BuildRequires: php5-pear >= 1.4.7
Requires: php5-pear-Horde_Exception < 2.0.0, php5-pear-Horde_Util < 2.0.0, php5-pear >= 1.7.0
Conflicts: php5-pear-Horde_Exception = 2.0.0, php5-pear-Horde_Util = 2.0.0
BuildRequires: php5-pear-channel-horde
Requires: php5-pear-channel-horde
BuildArch: noarch
BuildRequires: php-macros# Fix for renaming (package convention)
Provides: php5-pear-%{pear_sname} = %{version}
Provides: php-pear-%{pear_sname} = %{version}
Provides: pear-%{pear_sname} = %{version}
Obsoletes: php5-pear-%{pear_sname} < %{version}
Obsoletes: php-pear-%{pear_sname} < %{version}
Obsoletes: pear-%{pear_sname} < %{version}%description
The Horde_Auth package provides a common interface into the various
backends for the Horde authentication system.%prep
%setup -c%build
%install
%{__mv} package*.xml %{pear_name}-%{version}
cd %{pear_name}-%{version}
PHP_PEAR_PHP_BIN=”$(which php) -d memory_limit=50m”
%{__mkdir_p} %{buildroot}%{php_peardir}/.channels/
%{__cp} %{php_peardir}/.channels/pear.horde.org.reg \
%{buildroot}%{php_peardir}/.channels/
%{__pear} -v \
-d doc_dir=/doc \
-d bin_dir=%{_bindir} \
-d data_dir=%{php_peardir}/data \
-d test_dir=%{php_peardir}/tests \
install –offline –nodeps -R “%{buildroot}” package.xml%{__install} -D -m 0644 package.xml %{buildroot}%{php_pearxmldir}/%{pear_name}.xml
%{__rm} -rf %{buildroot}/{doc,tmp}
%{__rm} -rf %{buildroot}%{php_peardir}/.{filemap,lock,registry,channels,depdb,depdblock}cd ..
%php_pear_gen_filelist
%clean
rm -rf %{buildroot}%post
if [ "$1" = "1" ]; then
%{__pear} install –nodeps –soft –force –register-only %{php_pearxmldir}/%{pear_name}.xml
fi
if [ "$1" = "2" ]; then
%{__pear} upgrade –offline –register-only %{php_pearxmldir}/%{pear_name}.xml
fi%postun
if [ "$1" = "0" ]; then
%{__pear} uninstall –nodeps –ignore-errors –register-only pear.horde.org/%{pear_name}
fi%files -f %{name}.files
%defattr(-,root,root)
Two parts are marked black: First you have to include the channel package with “BuildRequires:”. Second marked part copies the channel file from the installed location to the buildroot location.
Feel free to reuse or criticise this solution.
Planet Horde
Last comments