Hi all,
ok - got it sorted after digging through older
linux vserver irclogs...
Solution was to add:
none /dev/shm tmpfs rw,nosuid,nodev,noexec 0 0
to '/etc/vservers/testbed/fstab' and to obviously
restart the vserver afterwards.
It now starts up just fine (and seems to work).
cheers,
fra
Hi all,
we're following 3.4.x (currently 3.4.11) closely and decided
to upgrade to 3.5.1 in a test environment today:
Environment (test+production) is linux vserver based:
host system: Debian Wheezy 7.8 x64
guest system:Debian Wheezy 7.8 x64
kernel+vs patch: 3.14.27-vs2.3.6.14
an