1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
|
diff -aur dcron-4.4/chuser.c dcron-4.4.logname/chuser.c
--- dcron-4.4/chuser.c 2010-02-15 11:18:13.111967483 +0100
+++ dcron-4.4.logname/chuser.c 2010-02-15 11:18:29.615531204 +0100
@@ -25,6 +25,7 @@
return(-1);
}
setenv("USER", pas->pw_name, 1);
+ setenv("LOGNAME", pas->pw_name, 1);
setenv("HOME", pas->pw_dir, 1);
setenv("SHELL", "/bin/sh", 1);
diff -aur dcron-4.4/crontab.1 dcron-4.4.logname/crontab.1
--- dcron-4.4/crontab.1 2010-02-15 11:18:13.111967483 +0100
+++ dcron-4.4.logname/crontab.1 2010-02-15 11:19:48.295707950 +0100
@@ -57,8 +57,8 @@
.PP
Nor does it do any special environment handling.
A shell script is better-suited to doing that than a cron daemon.
-This cron daemon sets up only three environment variables: USER,
-HOME, and SHELL.
+This cron daemon sets up only four environment variables: USER,
+LOGNAME, HOME, and SHELL.
.PP
Our crontab format is roughly similar to that used by vixiecron.
Individual fields may contain a time, a time range, a time range
|
