Goto:
http://www.vmware.com/download/server/
Right under Download VMware Server (in orange) you will see a link
that reads register for your free serial number(s).
On Dec 21, 2007 3:33 PM, Kevin O'Gorman [EMAIL PROTECTED] wrote:
I've emerged and partly configured vmware-server-1.0.4, but it is
The only things that I can guess are that it is trying to update
something in /proc or it needs to load a kernel module before
writing.
Just for fun - try burning a disk as root. Then try burning another
dist as a non-root user. If the the second disk burns then one or the
other of the above is
This process is the ssh daemon:
root 2988 1 0 Sep04 ?00:00:00 /usr/sbin/sshd
Two things: before killing the process with the KILL signal, I would
try killing it with TERM
kill -TERM 2988
If that doesn't work then kill the process with the KILL signal.
I would also use:
Try changing:
ScriptAlias /awstats
/usr/share/webapps/awstats/6.5-r1/hostroot/cgi-bin/awstats.pl
ScriptAlias /awstats.pl
/usr/share/webapps/awstats/6.5-r1/hostroot/cgi-bin/awstats.pl
To:
ScriptAlias /awstats /usr/share/webapps/awstats/6.5-r1/hostroot/cgi-bin
Also I specifically include:
Yes. As a personal preference I don't usually chain commands together
when trouble shooting something, but there is technically nothing
wrong with doing so.
-Stephen
On 9/10/07, Grant [EMAIL PROTECTED] wrote:
This process is the ssh daemon:
root 2988 1 0 Sep04 ?00:00:00
Killing the ssh daemon does not effect any of the existing
connections. The ssh daemon is used to listen for new connections and
create a process to handle communications with that request. That is
why when you update configuration parameters for sshd, they do not
take effect until the next
I think that there may be something significantly wrong with your box
(or configuration of sshd). I have never had a server disconnect an
active connection when killing the ssh daemon.
If there is someone that you can contact in the data center I would ask them to:
1) Backup your current
Stephen Wittig wrote:
Killing the ssh daemon does not effect any of the existing
connections. The ssh daemon is used to listen for new connections and
create a process to handle communications with that request. That is
why when you update configuration parameters for sshd, they do
The current init script will not try to restart the daemon if
everything does not exit cleanly. We already know that the main
process won't exit cleanly since it was manually killed.
Unless you are comfortable editing the init script I would suggest:
1) Type:
ps auxww |grep /usr/sbin/sshd |grep
Complete Side Note:
Does anyone know where to issue a bug report to try to have this
behavior changed. The correct (and more widely) seen behavior of
http://bugzilla.gentoo.org I guess.
Now, I know why I have never tried to submit a bug report before :)
--
[EMAIL PROTECTED] mailing list
10 matches
Mail list logo
