Re: [DNG] Ascii install in VM
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 wasn't a netmask setting. Removed the '/24' and added 'netmask 255.255.255.0' Restarted wicd, but still no network, so checked the wicd log and found this: 2018/03/04 16:24:39 :: Running command ['ifconfig', 'eth0' failed: [Errno 2] No such file or directory Bit of a chicken and egg situation here ;-) No network because net-tools isn't installed and I need network to install net-tools Thinking laterally, I removed 'wicd wicd-gtk wicd-daemon python-wicd wpasupplicant' and rebooted. I now had my fixed IP. Re-installed the packages I had removed and rebooted again, wicd now worked correctly. If Devuan wants to continue using wicd, I think it is going to have to install net-tools as part of the install. Rowland ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] pam_limits or limits.conf different from Debian?
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 (apparently) are all the things that frustrate people like me :) Thanks On 02/03/18 12:02, KatolaZ wrote: On Thu, Mar 01, 2018 at 10:50:23PM +, 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 distros. in Debian I can edit /etc/security/limits.conf and set * soft nofile 1 to be able to open the projects with more than 1000 layers without seeing rejected file open requests and crashes from the software This seems not to work in Devuan 2.0. Is there a hard limit somewhere else of less than 1000 or is a different configuration system used (even though this file is present) Just a (possibly unrelated) random thought: I guess you have already had a look at `ulimit -n`, right? Another possibly unrelated thought: if you have mangled with /etc/pam.d/login, you must make sure that it contains: sessionrequired pam_limits.so otherwise /etc/security/limits.conf gets ignored. You might also want to check if you have anything in /etc/security/limits.d Also, when you sets new limits the changes will apply only after you logout and login again. Also, you could check the system-wide file limit at /proc/sys/fs/file-max (unlikely to be a problem) Sorry if I have stated obvious facts at any point. HTH KatolaZ ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] pam_limits or limits.conf different from Debian?
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 open limit usually preset to 1000 in many distros. in Debian I can edit /etc/security/limits.conf and set * soft nofile 1 to be able to open the projects with more than 1000 layers without seeing rejected file open requests and crashes from the software This seems not to work in Devuan 2.0. Is there a hard limit somewhere else of less than 1000 or is a different configuration system used (even though this file is present) Just a (possibly unrelated) random thought: I guess you have already had a look at `ulimit -n`, right? My2Cents KatolaZ ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] pam_limits or limits.conf different from Debian?
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 distros. in Debian I can edit /etc/security/limits.conf and set * soft nofile 1 to be able to open the projects with more than 1000 layers without seeing rejected file open requests and crashes from the software This seems not to work in Devuan 2.0. Is there a hard limit somewhere else of less than 1000 or is a different configuration system used (even though this file is present) Just a (possibly unrelated) random thought: I guess you have already had a look at `ulimit -n`, right? My2Cents KatolaZ ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] pam_limits or limits.conf different from Debian?
I did some more tweaking, and basically it looks like I have to set the hard limit higher as well as the soft limit, in /etc/security/limits.conf The hard limit in Debian must be set higher somewhere else, because you don't have to set that one in the same file normally. Thanks for your 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 Devuan VM. The subtleties of why one distro would use one mechanism and a similar one a different mechanism (apparently) are all the things that frustrate people like me :) The thing is that I guess Devuan ASCII has not (willingly) changed any default in that respect, so the same problem might be present in debian stretch. This post: https://stackoverflow.com/questions/46441602/how-to-change-open-files-ulimit-n-permanently-for-normal-user-in-debian-stret suggests that libpam-systemd seems to ignore /etc/security/limits.conf by default. The easy way to check is by logging in from a tty, and looking at: $ ulimit -n I tried it now, setting nofile to 2, and it correctly shows the new value. Which polkit backend are you using? We might have inherited an unwanted behaviour in libpam-elogind, possibly. HND KatolaZ ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Network initialisation fail in Devuan 2.0
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 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
