I want to set up a crontab so that from my machine {which is 192.168.0.99}
whatever I create in a directory called "/information" {suppose some texts files}will be copied to 192.168.0.100 and 192.168.0.101's machine "/readinfo" directory at 5.30 pm. everyday.

"/readinfo" is directory which is accessible by all users on that machines {192.168.0.100 & 192.168.0.101}

is this crontab right?

30 5 * * * /bin/cp -rf /information/* 192.168.0.100:/readinfo
30 5 * * * /bin/cp -rf /information/* 192.168.0.101:/readinfo

I guess first these 100 and 101 machines should allow me {99} ssh connection without passowrd.
What if this ssh connection setting is done then ?

You'll want to use the command scp instead of cp since cp isn't aware of the network. What will happen with your crontab as is is that you'll copy all files in information to a directory called 192.168.0.100:/readinfo in whatever your corn's working directory is. scp copies files over an SSH connection and can be setup to not require a password with SSH keys. If you have any more questions just let us know.

Regards,

Alunduil

Crontab is right, but your commands are wrong. You can't do a regular copy to another machine...that would be SCP, which uses SSH. Unless the information directory is in your root, that path is wrong...same with the /readinfo destination. Also, you're not specifying a user, so by default, it's going to use root, which will probably fail. Anyone who is even halfway smart will always deny root access over the network.

The syntax for scp is well documented...most folks that have an RHCE and other certifications should know this.

Why do you talk about my RHCE again and again?
Don't get personal!
If you don't want to give me proper answer live it!
DON'T UNDERESTIMATE OTHERS!

...more fundamentally:
What problem are you trying to overcome that "/readinfo" should be "accessible by all users on that machines"?
Why are you opting for "push" instead of "pull"? Push makes the server responsible while pull is the clients concern:
- With a small HTTP server like Thy and 'curl' on the client side you could let the client pull in files.
- With a Xinetd entry and 'rsync' you could do the same.
- The same goes for anonymous read-only FTP.

I gave you "proper answer", but you either didn't read it, or don't understand it.

Why mention your supposed RHCE? Because you keep asking very, VERY basic questions, that ANYONE who was awake for an RHCE course, could answer. Pay attention to the answers given to you.