ls -R

Unusual Tasks With File Listings

When you create a new GPG key it wants you to wiggle the mouse or pound the keyboard or do something to create enough entropy to create a well-randomized key. There is an easy way, and that is to use the ls command to recursively list every file on your system:

$ ls -R /

Do this in a separate terminal, and then you don't have to do silly tiring things like wiggling mice. While we're on the subject of the ls command, you can list multiple directories in a single command by using simple wildcards:

$ sudo ls -l /var/*/*/

You can skip over subdirectories, as this example shows:

$ sudo ls -l /var/.../*/

I'm sure I copied this one from somewhere-- It draws a nice ASCII file tree of all subdirectories of the current directory:

$ find . -type d |sed 's:[^-][^/]*/:--:g; s:^-: |:'

Find Duplicate Files

The sure-fire way to find duplicate files is by comparing MD5 hashes. This compares only the first 20 characters of the md5sum, but it still takes a long time. It's the most accurate method, so I don't mind the wait:

$ find . -type f -exec md5sum '{}' ';' | sort | uniq --all-repeated=separate -w 20

You can also compare file sizes, which is a little less accurate but a lot faster:

$ find . -type f -printf "%p - %s" | sort -nr -k3 | uniq -D -f1

I use the first method when I start accumulating a lot of sloppy backups, and have too many copies of the same files littering my backup servers.
Find more here
https://www.linux.com/learn/docs/660651-bag-of-fun-and-useful-random-linux-comman
--
Thanks and Regards
Bhaskar Ramaraju
http://www.linkedin.com/in/ramarajubhaskar

AdminConsole throws 404

On one of the developer's RAD 7.5.5.1 box, WTE 7.0.0.21 admin console thows 404 when accessed.
http://localhost:admin_port/ibm/console is the standard URL.
*[11/6/12 12:53:57:159 CST] 00000012 webcontainer  E com.ibm.ws.webcontainer.WebContainer handleRequest SRVE0255E: A WebGroup/Virtual Host to handle /ibm/console/login.do has not been defined.*
This is the error message what it shows in the SystemOut.log.

AdminConsole is a systemApp that comes with the installation. There few commands using which one can remove the console and reinstall the app and even restore the app.
Solution :
1. Remove the AdminConsole application
2. Re install the AdminConsole application

1. Remove the AdminConsole -
Goto that profile\bin in which the problem is occurring,
start the server process in that profile.
Issue the following command from command line, with administrative privileges when running on windows
wsadmin -f deployConfig.py remove
This command removes the Adminconfig app.
Restart the server
2. Re install the AdminConsole application
Make sure the server is up and running,
Goto that profile where the issue is occurring,
issue the following command from command line, with administrative privileges when running on windows
wsadmin -f deployConfig.py install

This command installs the AdminConsole.
After successful exit from the command, bounce the server process.

Access the AdminConsole. It worked for me.

InfoCenter URL for the above quoted commands -

http://pic.dhe.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/tcon_startstop.html

A composition unit with name MyApp already exists. Select a different application name.

Problem(Abstract)

A composition unit with name MyApp already exists. Select a different application name.

Cause

This is most frequently observed during the installation or removal of applications, but it may also turn up during other administration tasks such as deleting servers.
The issue maybe caused by WebSphere Application Server APAR PM20642.

In this scenario, if there is an error with the deployment of a module, then this bad deployment is saved, then the WebSphere Application Server configuration will be out of sync.

In WebSphere Process Server, this often happens with a module that has WebSphere Business Integration Adapter Resources that might not be complete or set up properly.
When deploying using WebSphere Integration Developer using "Add Projects", the configuration changes for this bad deployment are automatically saved.

Even after the application is removed, you might not be able to do any further or new application installs or uninstalls (even with a corrected module).

Resolving the problem

The manual workaround is to delete the /blas and /cus directories for the bad application from the configuration.
The resources will be located in the config directory of the profile.:

<profile name>/config/cells/qcell/blas
<profile name>/config/cells/qcell/cus

http://www-01.ibm.com/support/docview.wss?uid=swg21455322
--
Thanks and Regards
Bhaskar Ramaraju
http://www.linkedin.com/in/ramarajubhaskar