In case neither cron.allow nor cron.deny exist in /etc/, which of the following is true?
In case neither cron.allow nor cron.deny exist in /etc/, which of the following is true?
If neither /etc/cron.allow nor /etc/cron.deny exist, the default behavior in many Unix-like systems is to allow all users to have user-specific crontabs. The files /etc/cron.allow and /etc/cron.deny are used to restrict or permit users to create and manage their own cron jobs. In their absence, no restrictions are applied, hence all users may have user-specific crontabs.
The correct answer is B. Without additional configuration, all users may have user specific crontabs. Explanation: The existence of /etc/cron.allow and /etc/cron.deny files is a way to control which users are allowed to use the crontab command to manage their own cron jobs. However, these files are optional. If neither file exists, the default behavior is to allow all users to create and manage their own crontabs. If only /etc/cron.allow exists, only the users listed in that file are allowed to use crontab. If only /etc/cron.deny exists, all users are allowed to use crontab except those listed in that file. If both files exist, /etc/cron.allow takes precedence. It's important to note that this behavior might vary slightly depending on the specific Linux distribution and its configuration. However, the general principle remains the same.