Bug 17860 - No choice for RHN login in bug reports; problems with the instructions on restarting the rhnsd service
Summary: No choice for RHN login in bug reports; problems with the instructions on res...
Alias: None
Product: Red Hat Web Site
Classification: Red Hat
Component: Other
Version: current
Hardware: i586
OS: Linux
Target Milestone: ---
Assignee: Tom Lancaster
QA Contact: Paul Lindner
URL: http://www.redhat.com/network/yn/adds...
Depends On:
TreeView+ depends on / blocked
Reported: 2000-09-26 15:18 UTC by Panic
Modified: 2007-04-18 16:28 UTC (History)
0 users

Clone Of:
Last Closed: 2000-09-26 18:13:09 UTC

Attachments (Terms of Use)

Description Panic 2000-09-26 15:18:59 UTC
There is no selection in Bugzilla under "Red Hat Web Site" to submit
problems with RHN registration, logins, etc.

The instructions at the above URL are wrong:

the /etc/rhnsd directory does not exist by default (on my system at least).
why in the hell do I have to manually rename the file and move it over?
the command you should have given for setting the service to "on" is:

chkconfig --level 345 rhnsd on

the "config" command does not exist.



Comment 1 Panic 2000-09-26 15:27:36 UTC
More -- the Your Network site did not display the profile that I created.  To
state the obvious, it looks like the RHN servers are not communicating with the
www.redhat.com/network site.

Comment 2 Panic 2000-09-26 17:36:11 UTC
It appears that the on-system client places the systemid file in
/etc/sysconfig/rhn/systemid -- shouldn't the web client do the same thing?

Comment 3 Panic 2000-09-26 18:13:07 UTC
saw the fix -- but it's still wrong. :)

you've got /etc/sysconfig/rhns/systemid, and it should be:


Also noticed that when a user switchs to the secure server, the link "Switch to
a secure server" is still on the page -- the pages are exactly the same, and its
a little confusing.

Comment 4 Paul Lindner 2000-09-26 23:49:37 UTC
There is a hidden category for RHNS (separate from web site)

I fixed the path.

Secure server switching should be fixed..

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