Bug 134597 – Change from using su to runuser in initscripts and cron jobs

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 134597 - Change from using su to runuser in initscripts and cron jobs

Summary:	Change from using su to runuser in initscripts and cron jobs

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	slrn (Show other bugs)
Sub Component:
Version:	rawhide
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Jindrich Novy
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2004-10-04 17:02 EDT by Daniel Walsh
Modified:	2013-07-02 19:02 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2004-10-06 11:38:02 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Daniel Walsh 2004-10-04 17:02:35 EDT

We have created a newversion of the su command called runuser, which
will run a program as a different user.  The command can only be run
as root and will not use pam or prompt for passwords.  Otherwise it
works exactly as su.  This change is needed by SELinux in order to
support proper transitioning on process execution.

Comment 1 Jindrich Novy 2004-10-06 10:04:42 EDT

Hi Dan,
are you sure slrn is the right package to complain about that? ;-)
I doubt slocate is the right one.

Comment 2 Daniel Walsh 2004-10-06 10:25:04 EDT

Not sure what you mean.

 /etc/cron.daily/slrnpull-expire contains a "su" command that should
be  changed to runuser.

Dan

Comment 3 Jindrich Novy 2004-10-06 11:38:02 EDT

Ok, slrn-0.9.8.0-1 fixed this.

Note You need to log in before you can comment on or make changes to this bug.