hello
vcontext: execvp("bash"): No such file or directory
what the meaning off??
how it could fixed.
more info were it come from see below.
T&BW
Roman
node3 ~ $vserver fc3 build -m rpm --hostname=fc3.yx.at --interface
eth0:192.168.2.29/24 --context 42 -- -d fc3 -b /mnt/cdrom/Fedora/RPMS/
-d fc3 -b /mnt/cdrom/Fedora/RPMS/ --
Warnung: package glibc = 2.3.3-74 was already added, replacing with glibc <=
2.3.3-74
Preparing... ###########################################
[100%]
1:setup ########################################### [
14%]
2:filesystem ########################################### [
29%]
3:basesystem ########################################### [
43%]
4:tzdata ########################################### [
57%]
5:glibc-common ########################################### [
71%]
6:libgcc ########################################### [
86%]
7:glibc ###########################################
[100%]
vcontext: execvp("bash"): No such file or directory
An error occured while executing the vserver startup sequence; when
there are no other messages, it is very likely that the init-script
(bash -c
exec >/dev/null
exec 2>/dev/null
set -x
f=/tmp/startwait
trap "rm -f $f" EXIT
mkfifo $f
( sleep 10; kill -s 9 -- -1 ) &
cat "$f" >/dev/null
kill -s 9 -- -1
wait
) failed.
Common causes are:
* /etc/rc.d/rc on Fedora Core 1 and RH9 fails always; the 'apt-rpm' build
method knows how to deal with this, but on existing installations,
appending 'true' to this file will help.
_______________________________________________
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
