A follow up from my last post.
I found out that server map is NOT the System.map file. It's referring
to the vsd conf files. It turns out that I had compiled freevsd from
the source. The install created /usr/local/etc/vsd and placed them
there. SO why I did was create a symbolic link to /etc/vsd. That got
past the error message.
Not the problem is that after I start vsd, I get no message:
[root@localhost /etc]# /etc/rc.d/init.d/vsd start
[root@localhost /etc]#
When I check the daemon status it says:
[root@localhost /etc]# /etc/rc.d/init.d/vsd status
vsd dead but subsys locked
Thing is that there is no log file or entry in /var/log/messages to give
me a clue what could be wrong. Has anyone seen this before? What do I
do to debug a little more?
Thanks,
pablo
On 02 Aug 2001 11:09:49 -0400, FreeVSD wrote:
> Hi,
>
> I am installing freevsd on a redhat 6.2 system that has been patched
> with a new kernel. It comes this way from my system vendor. The patch
> upgrades the kernel to 2.2.19 and other goodies.
>
> The problem I have is that after installing freevsd, I try to start the
> daemon and get an error:
>
> [root@localhost]# /etc/rc.d/init.d/vsd start
> couldn't read server map file: No such file or directory
>
> I think it's referring to the System.map file. I checked in my /boot
> directory and here is what I have:
>
> [root@localhost freevsd-1.4.9]# ls -l /boot
> total 40
> lrwxrwxrwx 1 root root 11 Jul 26 14:54 System.map ->
> /System.map
> -rw-r--r-- 1 root root 512 Apr 10 2000 boot.0300
> -rw-r--r-- 1 root root 512 Jul 26 14:58 boot.0800
> -rw-r--r-- 1 root root 4568 Feb 2 2000 boot.b
> -rw-r--r-- 1 root root 612 Feb 2 2000 chain.b
> -rw-r--r-- 1 root root 237 Apr 11 2000 kernel.h
> -rw------- 1 root root 12288 Jul 26 15:29 map
> -rw-r--r-- 1 root root 620 Feb 2 2000 os2_d.b
>
> The actually System.map file is sitting in the / directory as specified
> by the symbolic link. Why would this cause an error? Is there a
> specific string it's looking for? How do I find the place in the code
> where this is occuring? Or simply: How do I fix it so I can start the
> vsd daemon?
>
> Thank you!
>
> Pablo
>
>
>
> ------------------------- The freeVSD Support List --------------------------
> Subscribe: mailto:[EMAIL PROTECTED]?body=subscribe%20freevsd-support
> Unsubscribe: mailto:[EMAIL PROTECTED]?body=unsubscribe%20freevsd-support
> Archives: http://freevsd.org/support/mail-archives/freevsd-support
> -----------------------------------------------------------------------------
>
>
------------------------- The freeVSD Support List --------------------------
Subscribe: mailto:[EMAIL PROTECTED]?body=subscribe%20freevsd-support
Unsubscribe: mailto:[EMAIL PROTECTED]?body=unsubscribe%20freevsd-support
Archives: http://freevsd.org/support/mail-archives/freevsd-support
-----------------------------------------------------------------------------
