Bug 468337

Summary:	At Refuse to Work with Non-login Shell
Product:	[Fedora] Fedora	Reporter:	Qian Cai <qcai>
Component:	at	Assignee:	Marcela Mašláňová <mmaslano>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	high
Version:	10	CC:	mmaslano
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-12-03 09:31:38 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Qian Cai 2008-10-24 08:01:41 UTC

Description of problem:
The problem could be demonstrated by the following program running by root.

useradd -m foo
echo foo >/etc/at.allow
cat <<EOF >/home/foo/at
#!/bin/sh
echo "echo bar >/tmp/bar" | at now
EOF
chmod 777 /home/foo/at
su foo -c /home/foo/at
ls -l /tmp/bar

At does not schedule the job, and it is confusing that at does not show any warning or error message. 
ls: cannot access /tmp/bar: No such file or directory

It has the same problem with sudo.

It works with a login shell.
su foo -l -c /home/foo/at

Version-Release number of selected component (if applicable):
at-3.1.10-25.fc10.x86_64

How reproducible:
always

Steps to Reproduce:
See above.
  
Actual results:
ls: cannot access /tmp/bar: No such file or directory

Expected results:
/tmp/bar exists.

Comment 1 Bug Zapper 2008-11-26 04:11:23 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Marcela Mašláňová 2008-12-03 09:31:38 UTC

The job is in queue and it is scheduled. In foo's mail you can find failure of job.

The error message is quite abstract, but I suppose this is correct shell behaviour. foo doesn't have environment settings, so it can't run the command. After '-l' is used, than some enviroment variables for user are set.