I have to do ifdown ifup every time I start my VM
On 05/03/18 06:34, Rowland Penny wrote:
I installed Ascii in VM with a fixed IP and the install went without
any problems or errors, but when it rebooted, there was no network.
I checked and the ipaddress was set to '192.168.0.36/24' and there
Apologies if this already covered, I only got to this list recently.
When I start the VM the network comes up not functioning, and I have to
put in ifdown and then ifup to get it working.
This is a Virtualbox VM and has the Virtualbox guest extensions installed.
TIA
assistance.
On 02/03/18 21:28, KatolaZ wrote:
On Fri, Mar 02, 2018 at 02:13:15PM +1300, Patrick Dunford wrote:
No red flags for any of that stuff
On a Debian Buster VM where the increased file limit put into limits.conf
obviously works, the result of ulimit -n comes out the same 1024 as on my
setting a new value via ulimit is not effective and the value does not
persist in any case.
On 02/03/18 11:50, KatolaZ wrote:
On Fri, Mar 02, 2018 at 12:52:40AM +1300, BWK wrote:
Gidday all
I use qgis and have some projects in it that open over 1000 layers. This
runs up against the file
No red flags for any of that stuff
On a Debian Buster VM where the increased file limit put into
limits.conf obviously works, the result of ulimit -n comes out the same
1024 as on my Devuan VM.
The subtleties of why one distro would use one mechanism and a similar
one a different mechanism
It returns 1024
So what does that mean?
Thanks
On 02/03/18 11:50, KatolaZ wrote:
On Fri, Mar 02, 2018 at 12:52:40AM +1300, BWK wrote:
Gidday all
I use qgis and have some projects in it that open over 1000 layers. This
runs up against the file open limit usually preset to 1000 in many