Bug 247360 - ruserd doesn't start
ruserd doesn't start
Status: CLOSED DUPLICATE of bug 241219
Product: Fedora
Classification: Fedora
Component: rusers (Show other bugs)
powerpc Linux
low Severity medium
: ---
: ---
Assigned To: Jiri Moskovcak
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-07-07 17:41 EDT by Nigel Horne
Modified: 2015-02-01 17:47 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-07-11 04:50:18 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Nigel Horne 2007-07-07 17:41:08 EDT
Description of problem:
/etc/init.d/rusersd start gives 
/etc/init.d/rusersd: line 25: /etc/rc.d/init.d/portmap: No such file or directory

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. /etc/init.d/rusersd start
Actual results:
/etc/init.d/rusersd: line 25: /etc/rc.d/init.d/portmap: No such file or directory

Expected results:
Should start

Additional info:
Comment 1 Jiri Moskovcak 2007-07-11 04:17:45 EDT
The problem is, that portmap has been replaced by rpcbind in F7 and the init
script doesn't reflect this change. I don't have a PC with F7 installed, so I
can't fix it now, but I'll take a look at this problem later today.
Comment 2 Jiri Moskovcak 2007-07-11 04:50:18 EDT

*** This bug has been marked as a duplicate of 241219 ***

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