Databases Linux technews

Working with Oracle HTTP Server

In this blog i’m covering some basics on Oracle HTTP server(OHS) like

  • Checking OHS status.
  • Starting, stopping and restarting OHS.
  • Creating an Oracle HTTP server component.
  • Deleting an Oracle HTTP server component.

Checking OHS Status

We can determine the status of OHS by using the opmnctl command

$ORACLE_INSTANCE/bin/opmnctl status

Processes in Instance: instance1
ias-component                    | process-type       |     pid | status | Ports
ohs1                             | OHS                |    4789 | Alive  | https:1000, https:4444, http:7778

Starting, Stopping and restarting OHS

To Start use: >$ORACLE_INSTANCE/bin/opmnctl startall

To Stop use:  >$ORACLE_INSTANCE/bin/opmnctl stopproc process-type=OHS   or use  $ORACLE_INSTANCE/bin/opmnctl stopall

To restart: all Oracle HTTP Server components use: $ORACLE_INSTANCE/bin/opmnctl restartproc process-type=OHS

Creating an Oracle HTTP server component

The syntax for creating a Oracle HTTP server component is

$ORACLE_INSTANCE/bin/opmnctl createcomponent -componentType OHS -componentName component_name

For eg: to create an Oracle HTTP Server component named ohs1, use the following command:

>$ORACLE_INSTANCE/bin/opmnctl createcomponent -componentType OHS -componentName ohs1

When you create the Oracle HTTP Server component, ports are automatically assigned. However, you can use the following parameters to specify the ports of your choice:

-listenPort: HTTP listening port
-sslPort: HTTPS (SSL) listening port
-proxyPort: Proxy MBean port internally used by Oracle HTTP Server to communicate with Fusion Middleware Control

Deleting an Oracle HTTP server component

The syntax for deleting an Oracle HTTP server component using opmnctl is

>$ORACLE_INSTANCE/bin/opmnctl deletecomponent -componentName component_name

For eg: to delete an Oracle HTTP Server component named ohs1 use the following command:

>$ORACLE_INSTANCE/bin/opmnctl deletecomponent -componentName ohs1



An update on Google Affiliate Network

affiliate_network-500Our goal with Google Affiliate Network has been to help advertisers and publishers improve their performance across the affiliate ecosystem. Cost-per-action (CPA) marketing has rapidly evolved in the last few years, and we’ve invested significantly in CPA tools like Product Listing Ads, remarketing and Conversion Optimizer. We’re constantly evaluating our products to ensure that we’re focused on the services that will have the biggest impact for our advertisers and publishers.

To that end, we’ve made the difficult decision to retire Google Affiliate Network and focus on other products that are driving great results for clients.

We’ll continue to support our customers as we wind down the product over the next few months. And there are other products that can help you achieve your goals. Affiliate publishers can continue to earn AdSense revenue through the AdSense network. And marketers can take advantage of other CPA-oriented Google tools like Product Listing Ads, remarketing and Conversion Optimizer to drive valuable online sales and conversions. These areas are growing rapidly and we’re continuing to invest heavily in them.

Thanks for your support of our affiliate product, and we look forward to helping you grow your business in the future.

Read more @ google


Chrome Frame is declared obsolete by Google

In September 2009, one year after releasing the Chrome browser, Google unveiled “Chrome Frame”—a plugin that brought Chrome’s underlying technology to Internet Explorer. Google said Chrome Frame was necessary because users of IE, particularly its older versions, were missing out on HTML5, JavaScript performance improvements, and other modern Web technologies.

chrome_frame-430Webpages containing a tag pointing to Chrome Frame switch automatically to “Google Chrome’s speedy WebKit-based rendering engine” when the page detects that an IE user has Chrome Frame installed, according to Google. Chrome Frame runs on IE versions 6, 7, 8, and 9.

But today, Google said the plugin isn’t needed anymore and it will stop receiving support and updates entirely in January 2014. “It’s unusual to build something and hope it eventually makes itself obsolete, but in this case we see the retirement of Chrome Frame as evidence of just how far the Web has come,” Chrome engineer Robert Shield wrote in the Chromium blog

Dumping Chrome Frame could cause a bit of grief for developers, as some commenters on Shield’s blog post and on Hacker News point out. Google contends that there won’t be too many annoyances and that there are fixes for those that will exist. On the whole, Google believes Web development today is a less frustrating experience than it was when Chrome Frame was devised.


KDE Releases Beta of Plasma Workspaces, Applications and Platform 4.11

Today KDE released the beta of the new 4.11 versions of Workspaces, Applications, and Development Platform. With API, dependency and feature freezes in place, the KDE team’s focus is now on fixing bugs and further polishing.

Changes to KWalletManager and Okular

The 4.11 releases include many substantial changes and improvements, including:

  • Deeper integration of Qt Quick in Plasma Workspaces
  • Faster Nepomuk indexing; massive performance optimizations, such as reading data is 6 or more times faster than previously
  • Kontact improvements—faster indexing, new theme editor, a lot of bug fixes
  • KWin—many OpenGL improvements, work on an OpenGL 3.1 core context and improved robustness, optimizations aimed at reducing CPU and memory overhead

More improvements can be found in the 4.11 Feature Plan.

With the large number of changes, the 4.11 releases need a thorough testing in order to maintain and improve the quality and user experience. Actual users are critical to maintaining high KDE quality, because developers simply cannot test every possible configuration. We’re counting on you to help find bugs early so they can be squashed before the final release. Please consider joining the 4.11 team by installing the beta and reporting any bugs.


Red Hat Software Collections 1.0 Beta Now Available

Red Hat announced the beta release of the Red Hat software collection 1.0. Red Hat Software collections 1.0 delivers the latest stable versions of some of the most popular web development languages and opensource databases.

redhatRed Hat Software Collections 1.0 Beta includes access to the latest stable versions of the following dynamic languages:

  • Ruby 1.9.3 with Rails 3.2.8, which delivers substantial performance improvements for web-based applications. This results in faster load times, improved unicode support and threading, and a large collection of ruby gems.
  • Python version 2.7, which includes new unit test features, faster I/O, and tools and back-ported features from Python 3 to make future migration easier.
  • Python version 3.3, which offers significant improvements in language consistency, Unicode performance, imports, and distribution of packages.
  • PHP version 5.4, which includes new language syntax, improved performance and reduced memory consumption, and a built-in web server in CLI mode to simplify development workflows and testing.
  • Perl version 5.16.3, which includes improved unicode support, performance enhancements, new debugging options, enhanced security, and a number of new and updated modules.
  • Technology Preview of node.js version 0.10, which delivers an easy to use module for handling streams, better error handling with domains, and performance improvements for web application development.

Red Hat Software Collections 1.0 Beta also includes access to the latest stable versions of the following runtime databases:

  • MariaDB version 5.5, which introduces an easy-to-adopt alternative for MySQL for Red Hat Enterprise Linux users. Binary compatibility allows MySQL users to drop-in MariaDB without converting data files.
  • MySQL version 5.5, which offers performance, scalability, and usability enhancements.
  • PostgreSQL version 9.2, which includes native JSON support, covering indexes, and significant improvements in replication, high availability and performance.

Red Hat Software Collections 1.0 Beta is available now for use with Red Hat Enterprise Linux 6 to customers and partners with select active Red Hat Enterprise Linux Server, Red Hat Enterprise Linux Workstation or developer-related subscriptions.


Oracle is bringing back Java time zone updating tool

java_DEV_120-294670432ed2b4a6Oracle is bringing back Java time zone updating tool and has reversed a decision it made to remove the “tzupdater” tool from public download. The tool is used to update Java’s internal time zone database and allows users to adjust Java installations so they reflect correct timezones from around the world. Oracle had decided to remove the “tzupdater” tool at the start of March as part of the company’s ending of public updates to Oracle JDK 6, only making the software available to customers with Java 6 support contracts.

Time zones are adjusted regularly around the world by local authorities and keeping synchronised can be a near constant task. The tz database, which used to be called the Olson database, acts as a reference for all this information.The tzupdater tool is built using that database, converted it into the format required by Java, and patches Java installations with the updated information. Oracle update Java to the latest time zone data in JDK and JRE releases whenever they release a maintenance or update version, but there are users who need to ensure they always have to most up to date version of the time zone database installed; for them, Java maintenance updates do not happen quickly enough.

In the announcement of the reversal, Oracle’s Henrik Stahl explained that the inability to update JDK 7’s time zone data was “not in line with our policy” and that “The most recent version of the Oracle JDK will always be available royalty free (including any tools required to keep it up to date)”. Oracle is, says Stahl, also looking for ways to reduce the gap between time zone database updates and JDK/JRE updates. The tzupdater tool is available to download as is documentation on its use.

Redhat technews

Red Hat confirms GNOME Classic Mode for RHEL 7

Red Hat confirms GNOME Classic Mode for RHEL 7, The engineering director for Red Hat Enterprise Linux (RHEL), Denise Dumas, has said that the upcoming version of the company’s enterprise Linux distribution will use GNOME 3’s Classic Mode by default. Dumas was talking to TechTarget ahead of the 2013 Red Hat Summit that is currently ongoing in Boston.

Read more @ h-online


Hacking into a Linux system

Here we are covering on topic “Hacking into a Linux system”. Passwords are one of the main mechanism to login to a system, in case of a Linux system it’s not different. If you have access to the root password you have access to the entire system. Here i’m covering a small tutorial for how to hacking into a Linux machine.

Hacking from single user mode

During startup of the system press any key to interrupt the Grub Loader

Linux Boot Screen

Press ‘e’ to edit, and go to the line starting with kernel (2nd line in almost all cases)

Linux Single User Mode

Press ‘e’ to edit and add ‘1’ at the end of the line after space after the last word, you can use ‘s’ also instead of ‘1’.

Adding this entry will force the system to start in “Single User mode” and skip the default run level. Press ‘enter’ to complete editing and press ‘b’ to continue the boot process.

Login into Single User Mode

Now you are logged into a single user mode.

Change root Password

We can issue the ‘passwd’ command to change the root user password.

Add new root Password

Note: if SELinux is enabled, the above ‘passwd’ command may return blank. If it is returned blank it means SELinux is enabled and in enforcing mode, hence we need to disable SELinux

For disabling SELinux, type ‘setenforce 0’ @ the terminal prompt.
#setenforce 0

FIX: So now we know how to login to a Linux system by hacking root password using single user mode. But what if we want to fix this vulnerability?

For password protecting single user mode, open file "/etc/rc1.d/S99single" and add the following line

exec sbin/sulogin

This should be added before

exec init -t1 s

Protect Single User Mode

Once the changes are made reboot to Single use mode and have a check, it will be asking for a password to login to Single user mode.

Login to Single User Mode




How to prevent changing root password from single user mode?

Here we are covering on how toprevent changing root password from single user mode?

open file “/etc/rc1.d/S99single” in your favourite editor and search for line.

exec init -t1 s

Just add the following line above it. save it an exit.

exec sbin/sulogin
Now before entering single user mode you will need to provide root password to proceed. Check again trying to enter single user mode after these changing above said file.


GNOME 3.10

GNOME 3.10 is expected in September and some of its newest features are beginning to appear in the 3.9 development branch. Version 3.9.2 is expected this week.

Here’s the few screenshots of the new Gnome version.


GNOME Music is a new app for, well, playing music. Of course, it can’t yet compete feature-wise with e.g. rhythmbox, but it looks fresh and promising. And it plays my music already.


GNOME Maps is a map viewer. It is still in its infancy – it does not do much yet beyond loading maps and showing me my location. But that will soon change.


Gitg is a git repository viewer. It has been around for a while. Recently, it has been rewritten in vala and it is getting a visual refresh this cycle.


Bijiben is a note-taking application, it was available as a ‘preview’ in 3.8 (and you can install it in Fedora 19 by running yum install bijiben). For 3.10, it will be much more feature-complete, data exchange with tomboy and online accounts is planned.


Totem is getting a face-lift, picking up user-interface elements from other GNOME 3 applications (while not losing any features).

Status menu

The GNOME shell status area may be getting a design update, combining most of the hardware controls into a single menu.