sorted by: recent | see :
popular
Content Tagged with support + linux
Thank You for Registering OpenOffice.org
opensource: del.icio.us tag/opensource
Software
office
linux
OpenOffice
Computer
opensource
support
Linux Staff Your Linux Guide
SourceLabs News
SourceLabs Debuts New Class of Tools for Open Source Linux and Java (Press Release) – (March 18, 2008)
CNET News – “Open-source support company SourceLabs on Tuesday launched a subscription service aimed at Linux developers and IT administrators who do their own support.”
(March 18, 2008)
O’Reilly Open Source – “Developers and open source system users will be particularly interested in a SourceLabs announcement of a service called Self-Support Suites that has been in beta since December.”
(March 18, 2008)
eWeek’s Linux-Watch – “A small start-up based in Seattle has started selling a ‘self-support’ tool for developers working with Java and/or Linux.”
(March 19, 2008)
SourceLabs is covered in the largest German IT publication – “Mit den “Self-Support Tools” will SourceLabs eine Alternative zu klassischen Supportverträgen bieten.”
(March 20, 2008)
SourceLabs builds momentum in Japan
(March 18, 2008)
Linux Magazine (Brazil) – “A SourceLabs pretende oferecer, através de ferramentas de self support , uma alternativa ao sistema clássico de suporte atualmente adotado pelo mercado corporativo.”
(March 22, 2008)
IT Jungle – “If you are a developer working at a major corporation or a small company and you want to use Linux and open source tools to create Java applications, there is very little possibility that your company is going to let you do that without getting tech support for the Linux and tools that you use.”
(March 18, 2008)
Seattle Times – “I keep waiting for a big tech company to buy SourceLabs, an open-source software and tools developer in Pioneer Square. Maybe the new product it’s launching today, SourceLabs’ Self-Support Suite, will speed the process.”
(March 18, 2008)
LinuxDevices.com – “A small start-up based in Seattle has started selling a ‘self-support’ tool for developers working with Java and/or Linux.”
(March 18, 2008)
GigaOm: Ostatic – “Could automated software support solutions come to the rescue? The jury’s still out on that, but I was interested in today’s announcement from SourceLabs regarding new Linux and Java self-support tools.”
(March 18, 2008)
Northwest Innovation – “Seattle-based SourceLabs said Tuesday that it has rolled out new tools to help support open source Java and Linux software.”
(March 18, 2008)
SysCon Media – “SourceLabs announced the availability of SASH 2 complete with a major new milestone – integrated support for Apache Tomcat.”
(Sep 9, 2007)
Java
linux
tomcat
SourceLabs
support
self-support
Using Syslog information with SourceLabs Linux Self-Support
Below is documentation for using SourceLabs Self-Support Suite for Linux and Open Source Java to gather, organize, and search Syslog messages.
You can setup syslog to connect to the relay. In this release, we only support syslog over UDP. To set this up, you need to modify your syslogd config file. Often this is in /etc/syslog.conf
To get started, you can add
. @relayMachineName:4657
This will send all your syslog messages to a machine named relayMachineName over port 4657. Port 4657 is the default port the relay listens to for Syslog UDP messages. You can change this in the relay’s property file. This properties file is located in the ‘conf’ directory of your relay installation (e.g. /opt/sourcelabs/relay/conf).
To filter the syslog messages sent to the relay, please read the syslog documentation or man pages for more information.
Syslog-ng:
You can also setup syslog-ng to use the relay. For the current version of the relay, you will need to use UDP logging to the relay instead of TCP. To set this up, you need to modify your syslog-ng config file. Often this is in /etc/syslog-ng.conf
To get started, you can add
destination d_relay { udp("relayMachineName ", port(4657)); };
log { source(s_sys); destination(d_relay); };
Assuming that you are using a default syslog-ng configuration where source ‘s_sys’ represents all syslog messages (modify source as necessary for your configuration),this will send all your syslog messages to a machine named relayMachineName over port 4657. Port 4657 is the default port the relay listens to for Syslog UDP messages. You can change this in the relay’s property file. This properties file is located in the ‘conf’ directory of your relay installation (e.g. /opt/sourcelabs/relay/conf).
To filter the syslog messages sent to the relay, please read the syslog documentation or man pages for more information.
Find more information about SourceLabs Self-Support Suite for LInux and Open Source Java
linux
centos
RedHat
syslog
SuSE
SourceLabs
logging
Ubuntu
Debian
support