Description of problem:
if chkconfig (miguidedly) called with an argument containing a slash, chkconfig
goes to far down the path of trying to create a symlink, failing ungracefully,
leaving one wondering what "half configuration" got left in place.  perhaps a
basename when vetting the argument?


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


[root@station195 init.d]# ./NetworkManagerDispatcher start
Starting NetworkManagerDispatcher daemon:                  [  OK  ]
[root@station195 init.d]# chkconfig ./NetworkManagerDispatcher on
failed to make symlink /etc/rc2.d/S98./NetworkManagerDispatcher: No such file or
directory
failed to make symlink /etc/rc3.d/S98./NetworkManagerDispatcher: No such file or
directory
failed to make symlink /etc/rc4.d/S98./NetworkManagerDispatcher: No such file or
directory
failed to make symlink /etc/rc5.d/S98./NetworkManagerDispatcher: No such file or
directory