From 9c9f480557479ad497187eec2e4f38c20c950eb4 Mon Sep 17 00:00:00 2001 From: Denis Peplin Date: Tue, 8 Jun 2004 11:41:49 +0000 Subject: [PATCH] Add tags around root user Minor whitespace fix --- en_US.ISO8859-1/books/handbook/config/chapter.sgml | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/en_US.ISO8859-1/books/handbook/config/chapter.sgml b/en_US.ISO8859-1/books/handbook/config/chapter.sgml index 6d9b06bf86..57a21fc4aa 100644 --- a/en_US.ISO8859-1/books/handbook/config/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/config/chapter.sgml @@ -441,7 +441,7 @@ exit 0 crontab files store information about specific functions which cron is supposed to perform at certain times. - + The cron utility uses two different types of configuration files, the system crontab and user crontabs. The only difference between these two formats is the sixth field. In the @@ -450,16 +450,17 @@ exit 0 as any user. In a user crontab, the sixth field is the command to run, and all commands run as the user who created the crontab; this is an important security feature. - + User crontabs allow individual users to schedule tasks without the need for root privileges. Commands in a user's crontab run with the permissions of the user who owns the crontab. - The root user can have a user crontab just like + + The root user can have a user crontab just like any other user. This one is different from /etc/crontab (the system crontab). Because of the system crontab, there's usually no need to create a user crontab - for root. + for root. Let us take a look at the /etc/crontab file