Bug 247360 - ruserd doesn't start
Summary: ruserd doesn't start
Status: CLOSED DUPLICATE of bug 241219
Alias: None
Product: Fedora
Classification: Fedora
Component: rusers
Version: 7
Hardware: powerpc
OS: Linux
Target Milestone: ---
Assignee: Jiri Moskovcak
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2007-07-07 21:41 UTC by Nigel Horne
Modified: 2015-02-01 22:47 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2007-07-11 08:50:18 UTC

Attachments (Terms of Use)

Description Nigel Horne 2007-07-07 21:41:08 UTC
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 08:17:45 UTC
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 08:50:18 UTC

*** 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.