The rule was copy yesterday’s files to …

But How to determine what was the yesterdays date?

The answer was in date man page.

Here are the parts from the script related to yesterday date:

$date -d '1 day ago' +'%Y/%m/%d'
2011/06/02

on Internet I’ve found also:

date --date='yesterday'
Thu Jun  2 14:01:28 EDT 2011

And (Bonus!!) if you want to go in future

date --date='tomorrow'
Sat Jun  4 14:04:29 EDT 2011

Happy scripting…

For more info:
man screen

Recently I experienced following error:
$ screen -r
Cannot open your terminal '/dev/pts/0' - please check.

After searching for solution I found several instructing to change permissions etc.

But different solution, almost “hack” is the one I like.
Before starting screen type:
script /dev/null
And after that you can type:
screen -r
Only drawback is that you need to type one additional exit for script to terminate.

Credits for this to Harry Jackson. Unfortunately the resource was not available so i did to put a link to the site.

Just type at terminal:

echo '82 43/25 43+65P80P82P73P76P32P70P79P79P76P10P' | dc

Here is the procedure to install it:

1. type whereis bash
2. cd to that folder
3. type make configure
4. make all install clean
5. take a cofee
6. type chsh -s /usr/local/bin/bash root to change the shell for root or replace root with username you want to change the shell.
7. Then relogin (logout and login) to enjoy bash shell

One of the popular choises, minly because of it’s portability is PuTTy only putty.exe is needed and no installation is required. In addition it is free.

Downside is that sometimes there are problems with terminal emulation – not necessary coming from putty, but still annoying.

One of my problems is that when vim is in insert mode arrow keys do not work. For long time I was no able to find solution to the problem, but finally i found one. Just type this in your home folder:

echo syntax enable > ~/.vimrc

This did the trick for me. Hope it helps to you too.

The 2.0.0.8 release fixed some 200 issues, but accidentally regressed a few things. Most users won’t see any difference or experience any problems, and those 200 fixes make the 2.0.0.8 update very valuable, but you should never have to choose functionality over security. So we’re working fast to understand and fix these problems, and will shortly be issuing a 2.0.0.9 update to address them. The specific problems are:

• Bug 400406 – Firefox will ignore the “clear” CSS property when used beneath a box that is using the “float” property. There is a temporary workaround JS/CSS code available for web developers with affected layouts.
• Bug 400467 – Windows Vista users will get “Java not found” or “Java not working” errors when trying to load Java applets after updating. To fix this, users can right-click the Firefox icon and “Run as administrator”, then browse to a page with a Java applet — doing this once will fix the problem and permanently restore Java functionality.
• Bug 396695 – Add-ons are disabled after updating. Users can fix this problem by opening their profile folder and removing three files (extensions.rdf, extensions.ini and extensions.cache)
• Bug 400421 – Removing a single area element from an image map will cause the entire map to disappear. There is no workaround available at this time.
• Bug 400735 – Some Windows users may experience crashes at startup. There is no workaround available at this time.

At Foundry27, customers and developers can access a wealth of resources relating to the QNX Neutrino RTOS and the QNX Momentics IDE, as well as to new community projects.

Finally one mature realtime kernel code is available …. (bad news is that it is released under dual licensing).

Do you still have those problems?

If so the tool you may need is called subversion and is available for Linux/Unix/MAC OS X and Windows.

How to use it?

It is relatively easy especially if you create local repository:

1. You need to install the binary version or compile from source code (the procedure is described for CentOS 5, but sould not be drastically different for other OS’s except fro installation part)

yum install subversion

2. Next step is to create repository – it must be done on the machine where repository will reside

svnadmin create <path to local directory>

3. After you create repository next step is to import data

svn import <folder> <repository> -m "<log message>"

Where:

• folder – direcrtory where your data reside
• repository – file:///<path to repository> Note there are 3 slashes
• log message – something meaninfull probably something like “first import”

4. Rename the folder

mv folder folder.beforesvn

5. Create working copy of the data

svn checkout <repository> <working copy>

6. Start working and send changes to repository with

svn commit

Note that you need to be in “working copy” folder.

Probably you will say that this is simple task just remove user home directory and his password, but appears that this is not.

First thing is that there is no single command that will do this task for you.

Let’s start:

1. Lock user – this is done with following command:

passwd -l <user_name>

This command will achieve it by changing the password to a value that cannot be matched by any possible encrypted value.

This command is usefull also for temporary disabling user account.

2. Search for and kill any user processes that still run

ps aux | grep -i ^<user_name>

kill -9 <PID number>

where <PID number> is the number in the column just after the user name.

3. Find all files that belong to this user

find / -user <user_name>|less

4. Decision time – decide do you want to keep those files or erase them. My suggestion is to backup them just in case.

5. List and remove any crontab jobs

List user cron jobs:

crontab -u <user_name -l

And if you see any entries remove them:

crontab -u <user_name> -r

6. Remove user from sudoers (if you use sudo)

visudo

7. Check any other applications as remote access, MySQL, Web App.
More extended howto

After quick review I’ve decided to erase them with rm command.

For my surprise when running the command:

/bin/rm *.tmp

I got following error message:

bash: /bin/rm: Argument list too long

Conclusion:Even rm command has his limits!

Solution: Get Plumber(Joking)
Actually only Pipe is needed.
By typing following command:

find . -name "*.tmp"|less

You will see list of the files and by replacing less with xargs /bin/rm those files will be erased. Can you skip previous step? Yes you can and it is not required, but you risk to erase a lot of data if you have syntax error.

find . -name "*.tmp"| xargs /bin/rm.

Depending on the number of files and your system speed after a while all files will be erased.

Done .