RDP in full screen mode [Remote Desktop by MSTSC command]

To adjust the remote desktop setting in full screen mode in Windows 7 please follow these steps

1. Start ”Remote Desktop Connection”.
2. Click on “Options”.
3. Click on the “Display” tab.
4. On “Display configuration” settings, you can change the “Remote Desktop Connection” display by moving the slider from  “Small to Large”.
5. By moving the “Slider” all the way to large, the display settings will automatically set to “Full Screen”.

And the best of all, after you have made and RDP connection succesfully, press:

Ctrl  Alt  Break

This will toggle your full screen mode !!

Using PS command to get Time a Process runs (etime) On Mac Unix etc

Its a simple command but very useful.

To see the results for a single process,  just add a grep at the end for the process' name. For example:

$ ps -ax -o etime,command -c | grep AnwarApp

Please note above that AnwarApp is nothing but your Process name.

You shall get a detailed running time information of this process the.

Result:
08-02:10:05 AnwarApp

This means that on my Mac, the AnwarApp has been running for eight days, two hours, ten minutes, and 5 seconds. 

I believe you got your work done.

So, cheers!!

Checking File system / Directory size in Linux : Learn "df -k" or "du -sh" *

Check Disk Space with the Commands du and df - Linux

Checking disk space in Linux is important for several reasons:

1. It helps to ensure that there is enough space available for the system to function properly. When the disk is full, the system can become slow or even crash.
2. Checking disk space helps identify any disk usage patterns that might indicate a problem, such as a runaway process or malware that is consuming disk space.
3. Monitoring disk space can help prevent data loss by identifying when disk space is running low and taking appropriate action.
4. It can also help in identifying when it is time to upgrade the storage capacity.
5. It helps in identifying the files and folder which are taking up more space and delete them if not needed.
6. It is also important for security as it can help identify any suspicious files or folders that might have been created by malware.
7. It can also help in monitoring the performance of the system and its capacity to handle more load.

Overall, checking disk space in Linux is an important aspect of maintaining a stable and secure system, and can help identify and prevent problems before they occur.

Linux (and Typically all UNIX based or UNIX alike systems including AIX, Solaris, MAc or CentOS) offer
two commands for checking out free disk space.

Now this is a quick post that I call it (Don't know how I missed it till now. Posting on request of an anonymous user)

1. Linux "df" command :
Report file system disk space usage. That is, it shows information about the file system on which each FILE resides, or all file systems by default.

Syntax:  df [OPTION]... [FILE]...
Mandatory arguments to long options are mandatory for short options too.
  -a, --all             include dummy file systems
  -B, --block-size=SIZE  use SIZE-byte blocks
  -h, --human-readable  print sizes in human readable format (e.g., 1K 234M 2G)
  -H, --si              likewise, but use powers of 1000 not 1024
  -i, --inodes          list inode information instead of block usage
  -k                    like --block-size=1K
  -l, --local           limit listing to local file systems
      --no-sync         do not invoke sync before getting usage info (default)
  -P, --portability     use the POSIX output format
      --sync            invoke sync before getting usage info
  -t, --type=TYPE       limit listing to file systems of type TYPE
  -T, --print-type      print file system type
  -x, --exclude-type=TYPE   limit listing to file systems not of type TYPE
  -v                    (ignored)
      --help     display this help and exit
      --version  output version information and exit
SIZE may be (or may be an integer optionally followed by) one of following:
kB 1000, K 1024, MB 1000*1000, M 1024*1024, and so on for G, T, P, E, Z, Y.

EG. I am in a directory. But "df" command has nothing to deal with that. It outputs current OVERALL status of the system and its partitions.


2. Linux "du" command :
Estimate file space usage. That is, it summarize disk usage of each FILE, recursively for directories.

Syntax: du [OPTION]... [FILE]...
Mandatory arguments to long options are mandatory for short options too.
  -a, --all             write counts for all files, not just directories
      --apparent-size   print apparent sizes, rather than disk usage; although
                          the apparent size is usually smaller, it may be
                          larger due to holes in (`sparse') files, internal
                          fragmentation, indirect blocks, and the like
  -B, --block-size=SIZE  use SIZE-byte blocks
  -b, --bytes           equivalent to `--apparent-size --block-size=1'
  -c, --total           produce a grand total
  -D, --dereference-args  dereference only symlinks that are listed on the
                          command line
      --files0-from=F   summarize disk usage of the NUL-terminated file
                          names specified in file F
  -H                    like --si, but also evokes a warning; will soon
                          change to be equivalent to --dereference-args (-D)
  -h, --human-readable  print sizes in human readable format (e.g., 1K 234M 2G)
      --si              like -h, but use powers of 1000 not 1024
  -k                    like --block-size=1K
  -l, --count-links     count sizes many times if hard linked
  -m                    like --block-size=1M
  -L, --dereference     dereference all symbolic links
  -P, --no-dereference  don't follow any symbolic links (this is the default)
  -0, --null            end each output line with 0 byte rather than newline
  -S, --separate-dirs   do not include size of subdirectories
  -s, --summarize       display only a total for each argument
  -x, --one-file-system  skip directories on different file systems
  -X FILE, --exclude-from=FILE  Exclude files that match any pattern in FILE.
      --exclude=PATTERN  Exclude files that match PATTERN.
      --max-depth=N     print the total for a directory (or file, with --all)
                          only if it is N or fewer levels below the command
                          line argument;  --max-depth=0 is the same as
                          --summarize
      --time            show time of the last modification of any file in the
                          directory, or any of its subdirectories
      --time=WORD       show time as WORD instead of modification time:
                          atime, access, use, ctime or status
      --time-style=STYLE  show times using style STYLE:
                          full-iso, long-iso, iso, +FORMAT
                          FORMAT is interpreted like `date'
      --help     display this help and exit
      --version  output version information and exit
SIZE may be (or may be an integer optionally followed by) one of following:
kB 1000, K 1024, MB 1000*1000, M 1024*1024, and so on for G, T, P, E, Z, Y.
EG. I am in a directory. The "du" command tells about that directory. For eg. the following picture directly outputs the total size of that folder.

Hope this acts like a quick guide to men and women trying to play with Linux and other UNIX alike systems. Cheers :)

By the way i remember a joke on unix that goes like this - Why did the man using UNIX spend all day at the terminal? Because he couldn't figure out how to use the "vi" command to exit!

Just to add more: Remember 3 important commands when you are sitting on a linux, solaris, AIX, FreeBSD, or Mac Box [Huh, enuff. Just remember Unix :)  ]

1. df
df command can get how much space is occupied and  how much available space

2. du
du is the abbreviation of “disk usage”, this command will progressively into each subdirectory

3. fdisk

fdisk can be used to  manage disk partitions. One can do tasks like create new partition or delete an existing partition

Google to retire Meebo Bar on June 6th 2013

An easy and handy tool to the publishers around the globe, Meebo Bar, is now sentenced to death. Come June 6, the Meebo Bar publishing tool will get retired by Google.

The Meebo Bar is a tool that publishers can put on their site to make it easier for users to discover, browse, and share content on their site. Here's an example of the bar on Budget Travel:
Meebo Bar came as a JavaScript plug-in that sits at the bottom of Web pages. It enabled a lot of different social interaction and sharing features.

So now the developers are asked remove the inactive Meebo code from their site as the Meebo Bar. In case they do not do so, teh Meebo bar would not appear after 6th, this month.

It is worthwhile to note that Google bought Meebo for approximately $100 million.

The snippet of the email I got from Google reads as follows-
"Dear Meebo Bar Publisher,
Five years ago, we launched the Meebo Bar to bring community, engagement, and revenue to publisher sites.
As part of the Google team, this continues to be our focus, but we want to best serve mobile and desktop publishers moving forward. Therefore, we have decided to focus our resources on initiatives like the recently launched Google+Sign-In (which includes interactive posts and over-the-air app installs) and the Google+ plug-ins.
This means we will retire the Meebo Bar, effective June 6, 2013."

So, the world is done with an era of Meebo.
Sic..Sic..

Dumpbin to Check Application/DLL Compiled Platform (x86 vs x64)

I will take this oppurtunity to extend my earlier post on finding .SO and .A compiled versions over Linux platforms. You can achive same target in Windows using the Dumpbin utilty. Dumpbin is a program in Visual Studio Tools that helps you display information about a binary file.

Though the utility is much useful, but here I anm only describing about how to use it to check whether a dll is build for x86 or x64 platform. I will dedicate some other post for more usages of Dumpbin.
PS: If you do not have Visual Studio, you have to get Dumpbin by some other means. But if you have MS Studia then it is prebundled with it.

Start Visual Studia Command prompt. One way to do so is:
1. Go to start menu, find your VS2010 application folder
2. In Visual Studio Tools, click on Visual Studio Command Prompt (2010)
3. A command prompt environment will be load.
4. Navigate to your assembly location. Type, dumpbin /headers your_assembly.dll. It will display the following for x86 dll and x64 dll respectively. See the highlighted areas

You can also type dumbin on command prompt to see various Command line arguments. Its easy, but important is that you must remember that this tool can help you do so.
:)