Re: Out of memory killer misconfigured?
On Fri, Apr 15, 2022 at 02:09:04AM +0100, piorunz wrote:
> On 01/04/2022 07:08, to...@tuxteam.de wrote:
[...]
> > See man (1) choom and search for oom in man (5) proc.
> Thanks! That's exactly what I needed. Amazing.
You're welcome :)
> Now, after I start the process, I run:
>
> Adjust to maximum setting (kills first):
> choom -p `pidof terminal64.exe` --adjust 1000
>
> Lower priority of a processes:
> renice 19 `pidof terminal64.exe`
>
> That way offending process will never hang or destabilize my system.
>
> I just wish that Linux kernel would give maximum oom score to process
> with most memory, that's so obvious!
To a certain extent, it does (see below).
> But instead, defaults are so bad,
> it kills everything but one offending process.
> Can this be reported as a bug against linux kernel in Debian bug track?
You can, of course, try. Your chances of success would be better
if you tried to understand what kind thoughts have gone into it,
and why it's not working for you. The way you are putting it, it
comes across (to me, at least!) as "what kind of stupid design
is this" (cf. your words: "obvious", "defaults so bad"). I know
you don't intend that, but, as you can imagine, it won't fly if
that's how others perceive it :-)
If you want to learn more about that, the Linux MM ("memory
management") people have set up a wiki for that:
https://linux-mm.org/OOM_Killer
Enjoy :)
(and yes, on my box, more memory-hungry processes have a higher
/proc//oom_score, so they seem to incur a higher risk of
being killed. The browser lies somewhat because it spawns quite
a few processes, but as a product of the propaganda industry,
lying is its second nature ;-)
Cheers
--
t
signature.asc
Description: PGP signature
Re: Hello
On Fri 15 Apr 2022 at 00:31:52 (+0200), sergioyraul wrote: > Im looking for a version debían gnome non-free with all private firmware but > I install two versions Which I believe were non-free but they were not.can > you give me a link that complies with that? https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/11.3.0-live+nonfree/ after which you need to click on the architecture (amd64/i386), which method of delivery (bittorrent/iso), and the DE you want (you said Gnome). Cheers, David.
Re: Out of memory killer misconfigured?
On 01/04/2022 07:08, to...@tuxteam.de wrote: On Tue, Mar 29, 2022 at 07:58:38PM +0100, piorunz wrote: On 29/03/2022 10:56, Sven Hoexter wrote: E.g. we now have PSI as an information source https://lwn.net/Articles/759781/ which can be used with the Facebook oomd or systemd-oomd to have userland control over which process to kill. Thanks, I've read this article. Unfortunately, this is just information tool which can be used by engineers and developers so design their own oomd. I am not a developer. Is there any config file I can edit so just simply ask oomd to kill most memory hugging process instead of entire system? See man (1) choom and search for oom in man (5) proc. Cheers Thanks! That's exactly what I needed. Amazing. Now, after I start the process, I run: Adjust to maximum setting (kills first): choom -p `pidof terminal64.exe` --adjust 1000 Lower priority of a processes: renice 19 `pidof terminal64.exe` That way offending process will never hang or destabilize my system. I just wish that Linux kernel would give maximum oom score to process with most memory, that's so obvious! But instead, defaults are so bad, it kills everything but one offending process. Can this be reported as a bug against linux kernel in Debian bug track? -- With kindest regards, Piotr. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄
Hello
Im looking for a version debían gnome non-free with all private firmware but I install two versions Which I believe were non-free but they were not.can you give me a link that complies with that? Sent using https://www.zoho.com/mail/
Problème de SMTP
Bonjour à tous, Depuis 2 jours, les SMTP refusent tout envoi de mails. smtp.bbox.fr , smtp.free.fr J'utilise le MUA Kmail et c'est idem avec Evolution. Voici le message : "Impossible d'envoyer le message : Le fichier ou le dossier Le contenu du message n'a pas été accepté. Le serveur a répondu : « 5.7.1 Spam Detected - Mail Rejected. Please see our policy at: http://postmaster.free.fr/#spam_detected » n'existe pas. Le message restera dans votre dossier « À envoyer » jusqu'à ce que le problème soit corrigé (par exemple une adresse non valable) ou que vous le déplaciez dans un autre dossier. Le protocole de transport suivant a été utilisé : free" D'autres messages disent "policy error". Par contre, avec le webmail de Free et Bbox, ça fonctionne, mais c'est tellement moins pratique qu'un MUA tel Kmail. Y a t-il des personnes sur la ML qui utilisent le smtp.bbox.fr ou smtp.free.fr qui auraient ce blocage total d'envois de mails ? Sinon, que peut-il se passer ? Merci, @+ A. Valmer
Re: Debian installer with a newer kernel
On Thu, 2022-04-14 at 11:18 -0400, Stefan Monnier wrote: > > I think it would be great to provide such a (semi-)official support > > for > > backported kernels in the installer again. There is probably a > > significant number of users which use testing, just because they > > can't > > install stable on their systems. > > Another approach is to use the "Debian testing" installer and later > adjust the system to "Debian stable". Package downgrades aren't supported, and I don't expect what you suggest would go well. -- Tixy
KDE: okular, dolphin, kate and other app don't restore after reboot
Hi, I have saved my session manually but since last upgrade plasma was updated and it doesn't restore the tab any more after a reboot. what setting should i check ? Debian/Sid Operating System: Debian GNU/Linux KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.14.0-1-amd64 (64-bit) Graphics Platform: X11
Re: Debian "Bookworm" Installation
Peter HB wrote: > >I've just attempted to Install "Bookworm" to a USB stick and it went >mostly to plan, apart from the fact that it won't boot. However that's >not the issue at hand: I can't find a way to persuade the installer's >partitioner to use GPT instead of the MS-DOS partitioning scheme. When you're partitioning, the installer will keep the partitioning type that is currently on a disk (GPT or MS-DOS). You can ask it to write a new blank partition table by hitting on the raw disk device. The default choice for the new partition table will depend on whether you have booted the installer in UEFI (GPT) or legacy BIOS (MS-DOS) mode. You can override the that choice, but depending on your setup you *may* need to use expert mode to be asked the question about which partition type to use. -- Steve McIntyre, Cambridge, UK.st...@einval.com "We're the technical experts. We were hired so that management could ignore our recommendations and tell us how to do our jobs." -- Mike Andrews
Re: Debian installer with a newer kernel
Thank you for your good hints, Andrew. My approach is different. I am in the lucky position that the question is of theoretical interest to me this time only, in the past I had cases where I had to use testing, because the kernel of the installer was too old to support basic functions of my hardware. On IRC I was recommended to build a custom image of the d-i. This was actually provided as a service in the past at https://kmuto.jp/debian/d-i/ but has been discontinued since long. I found a short description for changing the d-i kernel at https://wiki.debian.org/DebianInstaller/Modify/CustomKernel. I guess it should work, as long as the kernel is not too new for the rest of the system. I think it would be great to provide such a (semi-)official support for backported kernels in the installer again. There is probably a significant number of users which use testing, just because they can't install stable on their systems. Regards, Christian On 2022-04-14 12:00 UTC+0200, Andrew M.A. Cater wrote: > On Thu, Apr 14, 2022 at 11:16:00AM +0200, Christian Britz wrote: >> Hello dear Debianists, >> >> if a new system has at least basic hardware support by the kernel >> provided by the Debian installer, you can solve many hardware problems >> by installing a newer kernel from backports after the system setup. >> >> Is there a solution for the case where the installer kernel is too old >> for core components like storage system support? Is there a way to use >> the installer itself with a backports kernel? >> >> Regards, >> Christian >> -- >> http://www.cb-fraggle.de >> > > This is a hard one: the kernel, initial ram disk and firmware are all fairly > closely aligned in the install medium. > > If you can get through much of the installer with the d-i kernel: > > You may be able to drop down to a shell in the target environment - edit > /etc/apt/sources.list to add the backports repository. > > At the end, just before you exit - drop to the target shell once again and apt > install the new kernel and newer firmware. > > Rerun the grub-install step just to check - then exit. > > As you reboot, so the backports kernel should be first. > > If graphics card configuration/firmware is an issue: text mode expert install > may well help - the text mode install tries to find compatible VESA modes. > > In some sense: this is the issue of very new hardware - for any distribution - > and there's no good clear answer. Debian - on a two year release cycle now, > more or less - is at least ahead of Red Hat where the distribution may have > to be kept stable in kernel version and ABI but current for ten years > afterwards. > > All the very best, as ever, > > Andy Cater > -- http://www.cb-fraggle.de
Re: Debian installer with a newer kernel
On Thu, Apr 14, 2022 at 11:16:00AM +0200, Christian Britz wrote: > Hello dear Debianists, > > if a new system has at least basic hardware support by the kernel > provided by the Debian installer, you can solve many hardware problems > by installing a newer kernel from backports after the system setup. > > Is there a solution for the case where the installer kernel is too old > for core components like storage system support? Is there a way to use > the installer itself with a backports kernel? > > Regards, > Christian > -- > http://www.cb-fraggle.de > This is a hard one: the kernel, initial ram disk and firmware are all fairly closely aligned in the install medium. If you can get through much of the installer with the d-i kernel: You may be able to drop down to a shell in the target environment - edit /etc/apt/sources.list to add the backports repository. At the end, just before you exit - drop to the target shell once again and apt install the new kernel and newer firmware. Rerun the grub-install step just to check - then exit. As you reboot, so the backports kernel should be first. If graphics card configuration/firmware is an issue: text mode expert install may well help - the text mode install tries to find compatible VESA modes. In some sense: this is the issue of very new hardware - for any distribution - and there's no good clear answer. Debian - on a two year release cycle now, more or less - is at least ahead of Red Hat where the distribution may have to be kept stable in kernel version and ABI but current for ten years afterwards. All the very best, as ever, Andy Cater
Re: Help settings up sound card on Debian stable
On 4/14/22 02:07, Christian Britz wrote: On 2022-04-13 09:28 UTC+0200, Yvan Masson wrote: I have no idea of what you could do to make it work on stable, sorry. But did you try running testing? It would be probably simpler, and testing generally runs great. It seems to be more or less consent that you are not advised to run Debian Testing on a productive system, one of the reasons is security support. Is this system so new that it requires a kernel from testing? bullseye-backports has kernel 5.16.12, the kernel in testing is also a 5.16.x release. It will probably not take too much time until 5.17.x or 5.18.x will appear in bullseye-backports. Regards, Christian Exactly as Christian said. Will like to learn about sound card configuration in general as well, so any suggestion is appreciated. OpenPGP_signature Description: OpenPGP digital signature
Re: Help settings up sound card on Debian stable
On 4/13/22 00:28, Yvan Masson wrote: Le 12/04/2022 à 03:48, manp...@gmail.com a écrit : Hi, I have been trying to set up a Minisforum HX90[1] with Debian stable with backports. Most of the stuff works out of the box except sound, bluetooth, and Wi-Fi. Hi, I have no idea of what you could do to make it work on stable, sorry. But did you try running testing? It would be probably simpler, and testing generally runs great. Regards, Yvan Thanks, and no worries. The reason I haven't tried testing is that this is a semi-production system and I'd like the base system to be stable. Also I've seen some success story regarding this type of sound card on other Linux distributions with a sufficiently recent kernel (5.15-ish), so I'd like to at least try to make it work which will be a learning process. In the worst case I may just wait for bookworm to become stable next year :) OpenPGP_signature Description: OpenPGP digital signature
Debian installer with a newer kernel
Hello dear Debianists, if a new system has at least basic hardware support by the kernel provided by the Debian installer, you can solve many hardware problems by installing a newer kernel from backports after the system setup. Is there a solution for the case where the installer kernel is too old for core components like storage system support? Is there a way to use the installer itself with a backports kernel? Regards, Christian -- http://www.cb-fraggle.de
Re: Help settings up sound card on Debian stable
On 2022-04-13 09:28 UTC+0200, Yvan Masson wrote: > I have no idea of what you could do to make it work on stable, sorry. > But did you try running testing? It would be probably simpler, and > testing generally runs great. It seems to be more or less consent that you are not advised to run Debian Testing on a productive system, one of the reasons is security support. Is this system so new that it requires a kernel from testing? bullseye-backports has kernel 5.16.12, the kernel in testing is also a 5.16.x release. It will probably not take too much time until 5.17.x or 5.18.x will appear in bullseye-backports. Regards, Christian -- http://www.cb-fraggle.de
Re: Debian "Bookworm" Installation
On 2022-04-14 01:07 UTC+0200, Peter Hillier-Brook wrote: > I've just attempted to Install "Bookworm" to a USB stick and it went > mostly to plan, apart from the fact that it won't boot. However that's > not the issue at hand: I can't find a way to persuade the installer's > partitioner to use GPT instead of the MS-DOS partitioning scheme. The installer should choose UEFI or BIOS mode depending on the settings of your firmware. Do you have previous experiences with a non-usb storage? Regards, Christian -- http://www.cb-fraggle.de
Re: Comment réserver à un seul fichier des logs en provenance d'une application donnée
Le jeudi 14 avril 2022 à 08:40:03 UTC+2, Olivier a écrit : > Malheureusement, pour une raison bien mystérieuse, l'option --log > ampute les logs des colonnes IPfw et Portfw (on conserve les IPsrc, > IPdst mais pas l'IPfw) ! > Dans l'hypothèse où cette amputation ne serait réversible, il faut > jouer avec les logs complets qui sont présents dans journald, syslog > etc ... - Je peux bien sûr me tromper mais je suppose que natlog génère le même contenu de log quelle que soit la sortie qu'il alimente pour cela. Je suppose aussi que les outils de visualisation (cat, more, less, etc...) que tu utilises tronquent de leur propre initiative les lignes trop longues et qu'il faut donc leur spécifier un option adéquate pour éviter cela (pour ceux de ces outils qui en sont capables, je n'ai pas creusé, une lecture de la page man de l'outil utilisé serait sûrement utile). Je suppose aussi que journalctl, soit formate une sortie plus large permettant de ne pas tronquer les lignes, soit effectue un retour automatique de ligne, soit permet de lire une ligne trop longue en déplaçant vers la droite une sorte d'écran virtuel (j'ai pas testé et j'ai pas lu la page man) - tu peux aussi essayer l'option --log-data de natlog pour générer un fichier log contenant une ligne d'en-tête de champs puis des lignes de champs tabulées, pour voir ce que ça donne
Re: backing up backups
On 4/13/22 20:03, Default User wrote: On Wed, Apr 13, 2022 at 4:42 PM David Christensen wrote: As you find system administration commands that work, put them into scripts: #!/bin/sh sudo rsync -aAXHxvv --delete --info=progress2,stats2,name2 /media/default/MSD1/ /media/default/MSD2/ Use a version control system for system administration. Create a project for every machine. Check in system configuration files, scripts, partition table backups, encryption header backups, RAID header backups, etc.. Maintain a plain text log file with notes of what you did (e.g. console sessions), when, and why. Put your OS on a small, fast device (e.g. SSD) and put your data on an array of large devices (e.g. ZFS pool with one or more HDD mirrors). Backup both as before. Additionally, take images of your OS device. Yikes! David, I really think I am too old to learn all of that. But maybe I can learn at least some of it, over time. Please understand that I am not training to be a real system administrator, except that I guess anyone is (or should be able to be) actually the "system administrator" of their own computer(s). Anyway, thanks for the advice. I learned the above tools because they save time, save effort, and provide features I want. I use dd(1) and an external HDD for images. You will want to write scripts (like the simple example I previously showed). CVS has more than enough power for a single user/ system administrator, and is simpler than Git. Here are the common use-cases: 1. Install CVS (and SSH) on Debian: # apt-get install cvs openssh-client openssh-server 2. Create a CVS repository: # mkdir -p /var/local/cvs/dpchrist # cvs -d /var/local/cvs/dpchrist init # chown -R dpchrist:dpchrist /var/local/cvs/dpchrist 3. Add CVS client environment variables to your shell (adjust host and username as required): export CVSROOT=dpchr...@cvs.tracy.holgerdanske.com:/var/local/cvs/dpchrist export CVS_RSH=ssh 4. Create a project: $ mkdir -p import/myproject $ cd import/myproject $ touch .exists $ cvs import myproject dpchrist start 5. Check-out a working directory of a project from the repository: $ cd $ cvs co myproject 6. Add a file to the project working directory meta-data: $ cd myproject $ vi myfile $ cvs add myfile 7. See changes in the working directory compared to the repository: $ cvs diff 8. Bring in changes made elsewhere and checked-in to the repository: $ cvs update 9. Check-in working directory to the repository: $ cvs ci 10. Remove a file from the project: $ rm myfile $ cvs rm myfile See the GNU CVS manual for more information: https://www.gnu.org/software/trans-coord/manual/cvs/html_node/index.html ZFS is a new way of doing storage with disks, arrays, volumes, filesystems, etc., including backup/ restore (snapshots and replication). The learning curve is non-trivial. The Lucas book gave me enough confidence to go for it: https://mwl.io/nonfiction/os#fmzfs David
Re: Comment réserver à un seul fichier des logs en provenance d'une application donnée
Malheureusement, pour une raison bien mystérieuse, l'option --log ampute les logs des colonnes IPfw et Portfw (on conserve les IPsrc, IPdst mais pas l'IPfw) ! Dans l'hypothèse où cette amputation ne serait réversible, il faut jouer avec les logs complets qui sont présents dans journald, syslog etc ... Le jeu. 14 avr. 2022 à 00:27, didier gaumet a écrit : > > Salut, > > Je n'ai jamais utilisé natlog > > mais sa page man me suggère de s'intéresser à son fichier de configuration et > aux options de lancement: > --log=argument (pour désactiver le log système en activant le log dans un > fichier particulier) > et > --log-rotate=spec (pour la rotation et la rétention) > > par exemple > > pour spécifier où atterrit le logging: > --log=/chemin/de/ton/fichier.log > et pour une rotation d'un jour et une rétention de 365 jours, peut-être (je > ne suis pas sûr d'avoir compris la spécification du format): > --log-rotate=time[1]365 >
Re: Debian "Bookworm" Installation
David Christensen writes: > I use the d-i at the simplest level I can (e.g. text "Install" mode from the > main menu). From what I have observed, d-i detects if the host is using BIOS > or > UEFI, and chooses MBR or GPT partitioning accordingly. Assume the host > firmware > can operate as UEFI, I would use the CMOS Setup program to set the host > firmware > to UEFI and then boot d-i. It might be possible or even necessary to boot the USB-drive in UEFI mode. I have seen firmware interfaces which have this option when determining the boot order. I.e. just having the firmware be in UEFI mode might not be enough. Regards, Nathanael
