help me understand the difference between cron.daily and crontab -e
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Umm, on every Linux distro I know of, /bin/sh is linked to /bin/bash, so there shouldn't be any difference. The only possible catch may be with Slackware (which I run) which, for a few things (I think primarily during installation, though) uses the "ash" shell, a stripped-down shell that provides VERY basic functionality in exchange for a teeny-weeny roughly 63kB size.
I have the #!/bin/bash statement as the first line in the script although I am not sure it solves that problem. Withing the script, I use the "env" command (and sent he output to mail) to check the environmental variables in the script shell. I get the following:
The SHELL variable indicates a user's preferred shell for launching applications by other applications when they call upon a shell to perform work. It does not override the interpreter line at the top of an executable file. This is often confusing to new users, as they expect SHELL to match the name of their current shell.