summaryrefslogtreecommitdiff
path: root/source/a/dcron/dcron.manpage.paths.diff
diff options
context:
space:
mode:
Diffstat (limited to 'source/a/dcron/dcron.manpage.paths.diff')
-rw-r--r--source/a/dcron/dcron.manpage.paths.diff65
1 files changed, 65 insertions, 0 deletions
diff --git a/source/a/dcron/dcron.manpage.paths.diff b/source/a/dcron/dcron.manpage.paths.diff
new file mode 100644
index 00000000..afd9c3d1
--- /dev/null
+++ b/source/a/dcron/dcron.manpage.paths.diff
@@ -0,0 +1,65 @@
+--- ./crond.8.orig 2010-01-18 09:29:25.000000000 -0600
++++ ./crond.8 2010-02-11 17:22:36.000000000 -0600
+@@ -17,13 +17,13 @@
+ .RE
+ .TP
+ .B -c dir
+-directory of per-user crontabs (defaults to /var/spool/cron)
++directory of per-user crontabs (defaults to /var/spool/cron/crontabs)
+ .RS
+ .RE
+ .TP
+ .B -t dir
+ directory of timestamps for \@freq and FREQ=\&... jobs (defaults to
+-/var/spool/cronstamps)
++/var/spool/cron/cronstamps)
+ .RS
+ .RE
+ .TP
+@@ -172,7 +172,7 @@
+ \f[B]crontab\f[] notifies \f[B]crond\f[] that a user's crontab file
+ has been modified (or created or deleted) through the
+ \[lq]cron.update\[rq] file, which resides in the per-user crontabs
+-directory (usually /var/spool/cron).
++directory (usually /var/spool/cron/crontabs).
+ \f[B]crontab\f[] appends the filename of the modified crontab file
+ to \[lq]cron.update\[rq]; and \f[B]crond\f[] inspects this file to
+ determine when to reparse or otherwise update its internal list of
+@@ -180,7 +180,7 @@
+ .PP
+ Whenever a \[lq]cron.update\[rq] file is seen, \f[B]crond\f[] also
+ re-reads timestamp files from its timestamp directory (usually
+-/var/spool/cronstamps).
++/var/spool/cron/cronstamps).
+ Normally these will just mirror \f[B]crond\f[]'s own internal
+ representations, but this mechanism could be used to manually
+ notify \f[B]crond\f[] that you've externally updated the
+@@ -210,7 +210,7 @@
+ crontab to /etc/cron.d/foo.
+ .PP
+ The superuser has a per-user crontab along with other users.
+-It usually resides at /var/spool/cron/root.
++It usually resides at /var/spool/cron/crontabs/root.
+ .PP
+ Users can only have a crontab if they have an entry in /etc/passwd;
+ however they do not need to have login shell privileges.
+--- ./crontab.1.orig 2010-01-18 09:29:25.000000000 -0600
++++ ./crontab.1 2010-02-11 17:23:13.000000000 -0600
+@@ -45,7 +45,7 @@
+ different user and/or crontab directory.
+ .PP
+ The superuser also has his or her own per-user crontab, saved as
+-/var/spool/cron/root.
++/var/spool/cron/crontabs/root.
+ .PP
+ Unlike other cron daemons, this crond/crontab package doesn't try
+ to do everything under the sun.
+@@ -117,7 +117,7 @@
+ The formats \@hourly, \@daily, \@weekly, \@monthly, and \@yearly
+ need to update timestamp files when their jobs have been run.
+ The timestamp files are saved as
+-/var/spool/cronstamps/user.jobname.
++/var/spool/cron/cronstamps/user.jobname.
+ So for all of these formats, the cron command needs a jobname,
+ given by prefixing the command with \f[B]ID=jobname\f[].
+ (This syntax was chosen to maximize the chance that our crontab