Bug 795746

Description of problem:
This is a part of the original bug #634922. Renaming subsys files and pidfiles is not able to be fixed and tested easily as a fastrack, so it has been separated into this bug and can be fixed in some later release.

Version-Release number of selected component (if applicable):
rusers-server-0.17-59.el6.x86_64.rpm

How reproducible:
every-time

Steps to Reproduce:
1.run rpmlint -i rusers-server-0.17-59.el6.x86_64.rpm
  
Actual results:
rusers.spec: W: invalid-url Source2: rstatd.tar.gz
The value should be a valid, public HTTP, HTTPS, or FTP URL.

rusers.spec: W: invalid-url Source0: ftp://ftp.uk.linux.org/pub/linux/Networking/netkit/netkit-rusers-0.17.tar.gz <urlopen error [Errno -2] Name or service not known>
The value should be a valid, public HTTP, HTTPS, or FTP URL.

rusers-server.x86_64: E: incoherent-subsys /etc/rc.d/init.d/rusersd rpc.rusersd
The filename of your lock file in /var/lock/subsys/ is incoherent with your
actual init script name. For example, if your script name is httpd, you have
to use 'httpd' as the filename in your subsys directory. It is also possible
that rpmlint gets this wrong, especially if the init script contains
nontrivial shell variables and/or assignments.  These cases usually manifest
themselves when rpmlint reports that the subsys name starts a with '$'; in
these cases a warning instead of an error is reported and you should check the
script manually.

rusers-server.x86_64: E: incoherent-subsys /etc/rc.d/init.d/rusersd rpc.rusersd
The filename of your lock file in /var/lock/subsys/ is incoherent with your
actual init script name. For example, if your script name is httpd, you have
to use 'httpd' as the filename in your subsys directory. It is also possible
that rpmlint gets this wrong, especially if the init script contains
nontrivial shell variables and/or assignments.  These cases usually manifest
themselves when rpmlint reports that the subsys name starts a with '$'; in
these cases a warning instead of an error is reported and you should check the
script manually.

rusers-server.x86_64: E: incoherent-subsys /etc/rc.d/init.d/rstatd rpc.rstatd
The filename of your lock file in /var/lock/subsys/ is incoherent with your
actual init script name. For example, if your script name is httpd, you have
to use 'httpd' as the filename in your subsys directory. It is also possible
that rpmlint gets this wrong, especially if the init script contains
nontrivial shell variables and/or assignments.  These cases usually manifest
themselves when rpmlint reports that the subsys name starts a with '$'; in
these cases a warning instead of an error is reported and you should check the
script manually.

rusers-server.x86_64: E: incoherent-subsys /etc/rc.d/init.d/rstatd rpc.rstatd
The filename of your lock file in /var/lock/subsys/ is incoherent with your
actual init script name. For example, if your script name is httpd, you have
to use 'httpd' as the filename in your subsys directory. It is also possible
that rpmlint gets this wrong, especially if the init script contains
nontrivial shell variables and/or assignments.  These cases usually manifest
themselves when rpmlint reports that the subsys name starts a with '$'; in
these cases a warning instead of an error is reported and you should check the
script manually.

3 packages and 1 specfiles checked; 4 errors, 2 warnings.

Expected results:
no errors

Additional info:
The warnings with invalid urls were expected, because packages don't have an active upstream and FTP on linux.org hasn't been available for some time.