Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#18338 - [dcron] Don't set LOGNAME env variable

Attached to Project: Arch Linux
Opened by Michael Trunner (trunneml) - Monday, 15 February 2010, 10:29 GMT
Last edited by Paul Mattal (paul) - Tuesday, 02 March 2010, 11:58 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Paul Mattal (paul)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
The most standard cron daemons under Unix for example Solaris and hpux, setting the env field LOGNAME to the user under the cronjob is running.

From the HPUX manpage:
"cron supplies a default environment for every shell, defining:
HOME=user's-home-directory
LOGNAME=user's-login-id
PATH=/usr/bin:/usr/sbin:.
SHELL=/usr/bin/sh"

solaris 10:
"Users who desire to have their .profile executed must
explicitly do so in the crontab file. cron supplies a
default environment for every shell, defining HOME, LOGNAME,
SHELL(=/bin/sh), TZ, and PATH."

Same does Vixie Cron.

dcron should do the same to not break some programs that need the LOGNAME.
If added a patch that sets the LOGNAME environment variable and fixes the manpage.

Additional info:
* dcron 4.4

Steps to reproduce:
* read the dcron manpage :-)

   logname.patch (1 KiB)
This task depends upon

Closed by  Paul Mattal (paul)
Tuesday, 02 March 2010, 11:58 GMT
Reason for closing:  Fixed
Additional comments about closing:  This is in dcron 4.4-2.
Comment by Michael Trunner (trunneml) - Monday, 22 February 2010, 02:14 GMT
any response? :-)
Comment by Paul Mattal (paul) - Monday, 22 February 2010, 02:18 GMT
Funny you should ask; I'm building dcron 4.4-2 now, adding this patch, among other things.

Jim may also add this functionality upstream, but that's not certain yet.
Comment by Michael Trunner (trunneml) - Monday, 22 February 2010, 13:15 GMT
I think the patch is not that big change and brings a real compatibility improvement :-)
Comment by Jim Pryor (Profjim) - Tuesday, 23 February 2010, 13:16 GMT
Yes, I'll work this into the next upstream version of dcron. Will probably be dcron 5.0. As Paul said, this patch is applied to the next/current Arch dcron release 4.4-2.
Comment by Michael Trunner (trunneml) - Tuesday, 23 February 2010, 16:28 GMT
Nice. That sounds good.

Loading...