Re: [IPTABLES] Comment lister les paquets rejetés ?
Philippe Gras a écrit : Le 07/06/2014 23:05, nb a écrit : INPUT ne sert pas pour une connexion déjà établie, seulement pour l'établissement d'une connexion (paquet tcp syn) Non. INPUT voit passer *tous* les paquets IP reçus destinés à la machine qui n'ont pas été bloqués avant. Je n'ai pas vu de forum ou de liste dédiée à Iptables En anglais : Liste Debian : debian-firew...@lists.debian.org Liste du noyau : netfil...@vger.kernel.org Il existe apparemment une différence dans le traitement des paquets par iptable selon leur état. Non. Toute différence de traitement selon l'état du paquet ne peut provenir que des règles mises en place. La seule exception, c'est le fonctionnement de la table 'nat'. Si iptables ne fait pas ce que tu veux, alors c'est que ton jeu de règles est à revoir. -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: https://lists.debian.org/539c2bd2.6070...@plouf.fr.eu.org
Re: Réseau : comportement lorsque plusieurs routeurs par défaut sont définis.
David Guyot a écrit : Le vendredi 13 juin 2014 à 09:13:55 +0200, Yann Cohen a écrit: Bonjour, Je cherche à comprendre/connaître le comportement de la couche TCP/IP de linux lorsque plusieurs destinations par défaut sont configurées. L'exemple est simple, soit un hôte avec deux interfaces eth0 en 192.168.0.1/24 et eth1 en 192.168.1.1/24, sur chaque interface est déclaré un routeur par défaut 192.168.0.254 sur eth0 et 192.168.1.254 sur eth1. Si ma mémoire est bonne, dans ce cas, le noyau est incapable de choisir la bonne route et refuse de router les paquets vers quelque passerelle que ce soit. N'importe quoi. Le noyau utilise simplement une des routes. Il ne va pas chercher à savoir si elle est opérationnelle ou non, ni utiliser l'autre route dans ce dernier cas. Il y a certainement une logique dans la sélection de la route (la dernière créée, la première créee...) mais mon conseil est : ne comptez pas dessus, et appliquez la loi de Murphy : si vous pensez que telle route sera utilisée, alors le noyau prendra certainement l'autre. -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: https://lists.debian.org/539c30bd.6090...@plouf.fr.eu.org
Re: Réseau : comportement lorsque plusieurs routeurs par défaut sont définis.
Bonjour, Perso, j'en étais resté à l'idée qu'il ne fallait tout simplement pas définir plusieurs routes par défaut car comme son nom l'indique *la* route par défaut est unique (c'est *la* utilisée quand aucune autre route ne matche). Maintenant peut-être que ça se fait malgré tout, mais dans ma logique ça n'a pas de sens. -- François Lafont -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: https://lists.debian.org/lnhcls$li7$1...@ger.gmane.org
Re: Réseau : comportement lorsque plusieurs routeurs par défaut sont définis.
exacte. c'est ce qu'on surnomme aussi d'ailleurs la route de la dernière chance Le 14 juin 2014 13:46, Francois Lafont mathsatta...@free.fr a écrit : Bonjour, Perso, j'en étais resté à l'idée qu'il ne fallait tout simplement pas définir plusieurs routes par défaut car comme son nom l'indique *la* route par défaut est unique (c'est *la* utilisée quand aucune autre route ne matche). Maintenant peut-être que ça se fait malgré tout, mais dans ma logique ça n'a pas de sens. -- François Lafont -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: https://lists.debian.org/lnhcls$li7$1...@ger.gmane.org
Re: Réseau : comportement lorsque plusieurs routeurs par défaut sont définis.
Le 14/06/2014 13:46, Francois Lafont a écrit : *la* route par défaut est unique (c'est *la* utilisée quand aucune ^ Oups, désolé il manque un mot. Il faut lire : « c'est *la* route utilisée ... » -- François Lafont -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: https://lists.debian.org/lnhcpv$li7$2...@ger.gmane.org
Re: Réseau : comportement lorsque plusieurs routeurs par défaut sont définis.
On 06/14/2014 01:23 PM, Pascal Hambourg wrote: David Guyot a écrit : Le vendredi 13 juin 2014 à 09:13:55 +0200, Yann Cohen a écrit: Bonjour, Je cherche à comprendre/connaître le comportement de la couche TCP/IP de linux lorsque plusieurs destinations par défaut sont configurées. L'exemple est simple, soit un hôte avec deux interfaces eth0 en 192.168.0.1/24 et eth1 en 192.168.1.1/24, sur chaque interface est déclaré un routeur par défaut 192.168.0.254 sur eth0 et 192.168.1.254 sur eth1. Si ma mémoire est bonne, dans ce cas, le noyau est incapable de choisir la bonne route et refuse de router les paquets vers quelque passerelle que ce soit. N'importe quoi. Le noyau utilise simplement une des routes. Il ne va pas chercher à savoir si elle est opérationnelle ou non, ni utiliser l'autre route dans ce dernier cas. Il y a certainement une logique dans la sélection de la route (la dernière créée, la première créee...) mais mon conseil est : ne comptez pas dessus, et appliquez la loi de Murphy : si vous pensez que telle route sera utilisée, alors le noyau prendra certainement l'autre. Si la mémoire a moi :) est bonne.. Il faut considérer la route par défaut comme un fallback : si aucune route spéciale n'est définie pour un paquet donne, alors il utilise la route par défaut. Je crois.. ;) -- “One original thought is worth a thousand mindless quotings.” “Le vrai n'est pas plus sûr que le probable.” Diogene Laerce signature.asc Description: OpenPGP digital signature
Re: lenteur du reboot
le jeudi 12 juin 2014 à 10:47 (+0200), Sébastien NOBILI a écrit: Bonjour Seb, Certains BIOS ont une option de configuration du test de mémoire (RAM) pour permettre un test rapide au démarrage. Est-ce que ton BIOS ne lancerait pas un test complet (avec les capacités actuelles ça peut durer) quand tu rebootes ? Le BIOS a la fonction Quick Boot activée qui omet de faire des test pour accélérer le boot. Ton BIOS peut également te proposer de masquer (ou non) ses messages, en les affichant tu trouveras peut-être des informations intéressantes. Je n'ai pas trouvé ce genre de fonction. Comme le boot se fait correctement lors d'un démarrage à froid, je me demande si le problème ne viendrait pas d'informations résiduelles en RAM qui perturberaient le BIOS lors d'un reboot ? Merci pour ta réponse tes remarques utiles. -- Gérard -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: https://lists.debian.org/20140614140415.GA2986@crunchbang
Re: lenteur du reboot
le mercredi 11 juin 2014 à 19:51 (+0200), Raph a écrit: Bonjour Ralph, ça m'est arrivé sur un serveur HP proliant dL120 G5. Manifestement, nous avons une incompatibilité entre le BIOS ou le chipset du serveur et le grub-pc. Une solution au problème : http://ubuntuforums.org/showthread.php?t=942541 voir si avec votre modèle, il n'y a pas des cas similaires. D'après ce que j'ai pu lire dans la page Grub hanging booting Proliant DL120 G5, ça ne semble pas convenir au cas de ma machine. Je continue les recherches. Merci pour votre réponse. -- Gérard -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: https://lists.debian.org/20140614141402.GB2986@crunchbang
Re: lenteur du reboot
On 06/14/2014 04:04 PM, sTriX wrote: le jeudi 12 juin 2014 à 10:47 (+0200), Sébastien NOBILI a écrit: Bonjour Seb, Certains BIOS ont une option de configuration du test de mémoire (RAM) pour permettre un test rapide au démarrage. Est-ce que ton BIOS ne lancerait pas un test complet (avec les capacités actuelles ça peut durer) quand tu rebootes ? Le BIOS a la fonction Quick Boot activée qui omet de faire des test pour accélérer le boot. Ton BIOS peut également te proposer de masquer (ou non) ses messages, en les affichant tu trouveras peut-être des informations intéressantes. Je n'ai pas trouvé ce genre de fonction. Comme le boot se fait correctement lors d'un démarrage à froid, je me demande si le problème ne viendrait pas d'informations résiduelles en RAM qui perturberaient le BIOS lors d'un reboot ? Bonjour La première chose à faire est de regarder les log de bootlog et syslog. Un boot peut être lent à cause de services qui prennent du temps à démarrer (suite à des erreurs). -- Maderios -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: https://lists.debian.org/539c5915.1050...@gmail.com
Re: lenteur du reboot
le mercredi 11 juin 2014 à 21:25 (+0200), Louis Wiart a écrit: Bonjour Louis, Je dis peut être une bêtise, mais ça ne peut pas être une histoire de pile sur la carte mère ? La réponse n'était pas bête ; j'ai vérifié et ce n'est pas çà. Merci. -- Gérard -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: https://lists.debian.org/20140614142108.GC2986@crunchbang
Re: lenteur du reboot
On 06/14/2014 04:15 PM, maderios wrote: On 06/14/2014 04:04 PM, sTriX wrote: le jeudi 12 juin 2014 à 10:47 (+0200), Sébastien NOBILI a écrit: Bonjour Seb, Certains BIOS ont une option de configuration du test de mémoire (RAM) pour permettre un test rapide au démarrage. Est-ce que ton BIOS ne lancerait pas un test complet (avec les capacités actuelles ça peut durer) quand tu rebootes ? Le BIOS a la fonction Quick Boot activée qui omet de faire des test pour accélérer le boot. Ton BIOS peut également te proposer de masquer (ou non) ses messages, en les affichant tu trouveras peut-être des informations intéressantes. Je n'ai pas trouvé ce genre de fonction. Comme le boot se fait correctement lors d'un démarrage à froid, je me demande si le problème ne viendrait pas d'informations résiduelles en RAM qui perturberaient le BIOS lors d'un reboot ? Bonjour La première chose à faire est de regarder les log de bootlog et syslog. Un boot peut être lent à cause de services qui prennent du temps à démarrer (suite à des erreurs). Si je me rappelle bien ton premier message, le BIOS prend 3 mn avant de passer a GRUB : dans ce cas, c'est d'abord du cote matériel que je regarderais. Le fait que ce ne soit qu'en cas de redémarrage peut venir du fait que l'ordinateur/certaines pièces hardware ont deja chauffe et ne sont plus reconnus aussi facilement que froid(es). Es-tu sur de la fiabilité de toutes tes pièces hardware - RAM, disques,.. - Une carte graphique défectueuse m'avait donne le même genre de problème une fois ? Et surtout depuis quand/quel événement tu constates le problème ? -- “One original thought is worth a thousand mindless quotings.” “Le vrai n'est pas plus sûr que le probable.” Diogene Laerce signature.asc Description: OpenPGP digital signature
Re: lenteur du reboot
le samedi 14 juin 2014 à 16:15 (+0200), maderios a écrit: La première chose à faire est de regarder les log de bootlog et syslog. Un boot peut être lent à cause de services qui prennent du temps à démarrer (suite à des erreurs). Oui, je vais tenter une expédition dans le monde des logs. Mes connaissances informatiques étant assez limitées, et ne sachant pas exactement ce qu'il me faut chercher, il va me falloir une âme de Thésée entrant dans le labyrinthe... Je te tiendrais au courant si j'en ressort un jour sans m'être faits bouffer par le Minotaure. ;-) -- Gérard -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: https://lists.debian.org/20140614171634.GA2692@crunchbang
Re: lenteur du reboot
le samedi 14 juin 2014 à 16:28 (+0200), Diogene Laerce a écrit: Bonjour, Si je me rappelle bien ton premier message, le BIOS prend 3 mn avant de passer a GRUB : dans ce cas, c'est d'abord du cote matériel que je regarderais. Le fait que ce ne soit qu'en cas de redémarrage peut venir du fait que l'ordinateur/certaines pièces hardware ont deja chauffe et ne sont plus reconnus aussi facilement que froid(es). La piste du matériel et des composants chauds est en effet intéressante. J'ai fait un test simple : Ma machine étant en fonction depuis plus de 5 heures, je l'ai arrêté par un shutdown -halt now et dès son extinction je l'ai rallumé en moins d'une seconde pour ne pas laisser le temps aux divers composant de se refroidir. Résultat : le boot s'est comporté normalement, l'affichage de Grub est apparu en 10 secondes après le bip de boot. Es-tu sur de la fiabilité de toutes tes pièces hardware - RAM, disques,.. - Une carte graphique défectueuse m'avait donne le même genre de problème une fois ? Et surtout depuis quand/quel événement tu constates le problème ? Voilà un certain nombre d'années que je ne suis plus sûr de rien. Je dirais même que le sûr est aussi improbable que le vrai. ;-) Alors, pour ce qui est de la fiabilité matérielle... Ta remarque m'incite néanmoins à étudier cette piste. Et surtout depuis quand/quel événement tu constates le problème ? Quand ? Je ne sais pas précisément. Le système Debian étant un système informatique de réputation robuste stable, la pratique du reboot n'est pas chose courante. Par contre je m'en suis aperçu en m'essayant à la configuration d'openbox en avril dernier. Merci pour ta contribution. -- Gérard -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: https://lists.debian.org/20140614211947.GB2692@crunchbang
Re: lenteur du reboot
Le samedi 14 juin 2014 à 19:16 +0200, sTriX a écrit : le samedi 14 juin 2014 à 16:15 (+0200), maderios a écrit: La première chose à faire est de regarder les log de bootlog et syslog. Un boot peut être lent à cause de services qui prennent du temps à démarrer (suite à des erreurs). Oui, je vais tenter une expédition dans le monde des logs. Mes connaissances informatiques étant assez limitées, et ne sachant pas exactement ce qu'il me faut chercher, il va me falloir une âme de Thésée entrant dans le labyrinthe... Je te tiendrais au courant si j'en ressort un jour sans m'être faits bouffer par le Minotaure. ;-) -- Gérard Tu as essayé de croiser l'alim avec une autre, ou au minimum de vérifier les tensions des fois qu'il y ait un composant en train de dériver ? [Troll inside] Ton bios a bien été contrôlé par la NSA au moment de sa livraison ? [/Troll] [Troll inside] La télécommande de ton bios serait-elle foireuse ou incompatible ? https://korben.info/computrace-lojack-absolute.html[/Troll] -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: https://lists.debian.org/1402782009.8247.5.camel@azuki.jisui
Re: usnado contraseñas seguras
El Fri, 13 Jun 2014 11:47:40 -0400, Yoslan Raul Jimenez Carvajal escribió: resulta ser que estoy probando en un openvz con debian 7.5 libpam-cracklib y no me pone la restriccion aca pongo el howto por el que me he guiado pero no me funciona no se si es la version de debian o que la este corriendo en openvz (...) En este artículo¹ dice que tras instalar el paquete sólo tienes que ejecutar pam-auth-update para activarlo. En cualquier caso, revisa la documentación del propio paquete y la página del manual. ¹http://www.deb-admin.com/enforcing-strong-passwords-with-cracklib/ Saludos, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/pan.2014.06.14.14.50...@gmail.com
Re: [OT] Red Hat 7: XFS como sistema de archivos predeterminado
El Fri, 13 Jun 2014 20:15:31 +0200, Manolo Díaz escribió: (...) Hace unos días leí que había salido una nueva versión de Red Hat¹ (hasta aquí nada nuevo) pero me llamó la atención el cambio que habían hecho para el sistema de archivos que se instala como predeterminado pasando de Ext4 a XFS. (...) ¿Qué os parece? ¿A qué creéis que se debe el cambio: estrategia comercial decisión puramente técnica, una mezcla de ambas...? (...) Pues a mí también me intriga. Tenía entendido que ext4 era más estable que XFS en Linux, y desde luego está mucho más probado. Exactamente, de ahí que la recomendación resulte cuanto menos curiosa. No hay que olvidar que, como decía antes, XFS es un poco peculiar en algunos aspectos, entre otros: 1/ Alimentación constante (SAI) o te arriesgas a pérdida de datos 2/ No dispone de una herramienta undelete 3/ No permite reducciones en caliente Tal vez sea que un máximo de 16 TB por fichero y 50 TB para todo el sistema de fichero se les queda corto. Esto es lo más parecido a una justificación que parecen dar: https://access.redhat.com/site/documentation/en-US/ Red_Hat_Enterprise_Linux/7/html/Storage_Administration_Guide/ch-ext4.html Eso tendría sentido teniendo en cuenta el tipo de cliente al que se dirige Red Hat pero no olvidemos que de lo que se trata es de predeterminar XFS como sistema de archivos enla partición raíz (o eso es lo que yo he entendido) que las grandes empresas suelen tener en particiones de pequeño tamaño para minimizar riesgos y ubicadas en unidades de disco muy rápidas (SCSI, SAS o SSD) y no particiones de datos donde si se trabaja con archivos de tamaño gigántico donde vería más razonable esta nueva recomendación. Saludos, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/pan.2014.06.14.15.09...@gmail.com
Re: [OT] Red Hat 7: XFS como sistema de archivos predeterminado
On Sat, Jun 14, 2014 at 03:10:00PM +, Camaleón wrote: No hay que olvidar que, como decía antes, XFS es un poco peculiar en algunos aspectos, entre otros: 2/ No dispone de una herramienta undelete Ojo. En Unix, tradicionalmente, nunca ha habido undelete. En todo caso lo peculiar es que lo haya, no que no lo haya. -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140614181933.ga7...@cantor.unex.es
SOLVED: Re: Can Iceweasel and Firefox co-exist on Wheezy.
On Saturday 14 June 2014 06:48:27 Dmitrii Kashin wrote: Lisi Reisz lisi.re...@gmail.com writes: On Friday 13 June 2014 20:34:12 Dmitrii Kashin wrote: Lisi Reisz lisi.re...@gmail.com writes: I am giving up in despair and I'm going to install Firefox. :-( Just too many sites won't talk to me. Do I need to uninstall Iceweasel first or can I have both? TDE 3.5.13.2 on Wheezy 7.5. Lisi Lisi, it seems that all you really want is to browse all these sites, right? Why don't you install the most fresh iceweasel's version from wheezy-backports as Mozilla Debian Team recommends[1]? [1] http://mozilla.debian.net/ I have. ?! But Lisi, your words: I have: Version: 24.5.0esr-1~deb7u1 according to aptitude show iceweasel. And 24.5.0 according to Iceweasel itself. And mozilla.debian.net repository contains quite more resent version: # apt-cache policy iceweasel iceweasel: Installed: 29.0.1-2 Candidate: 30.0-1~bpo70+1 Version table: ... 30.0-1~bpo70+1 0 500 http://mozilla.debian.net/ wheezy-backports/iceweasel-release amd64 Packages ... 24.4.0esr-1~deb7u2 0 500 file:/home/mirror/pool/ wheezy/main amd64 Packages ... Are you sure you *have* installed iceweasel from backports? Have some problems disappeared after upgrade to iceweasel-v30? I was entirely sure I had asked to install from backports, so this further email from you made me explore why, if I had not, I had not succeeded. The answer? I still had: deb http://mozilla.debian.net wheezy-backports iceweasel-esr icedove-esr in my sources list when it should now have been: deb http://mozilla.debian.net wheezy-backports iceweasel-esr icedove-release One short edit of my sources list later, I now have Iceweasel 30. Thank you!! :-) Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201406140857.20611.lisi.re...@gmail.com
CORRIGENDA - Re: SOLVED: Re: Can Iceweasel and Firefox co-exist on Wheezy.
On Saturday 14 June 2014 08:57:20 Lisi Reisz wrote: deb http://mozilla.debian.net wheezy-backports iceweasel-esr icedove-release Sorry. :-( deb http://mozilla.debian.net wheezy-backports iceweasel-release I must be more careful with my copying and pasting. :-( Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201406140859.40338.lisi.re...@gmail.com
Re: Can Iceweasel and Firefox co-exist on Wheezy.
On Friday 13 June 2014 19:17:19 Go Linux wrote: On Fri, 6/13/14, Lisi Reisz lisi.re...@gmail.com wrote: Subject: Re: Can Iceweasel and Firefox co-exist on Wheezy. To: debian-user@lists.debian.org Date: Friday, June 13, 2014, 9:01 AM https://beta.ovoenergy.com/login I can't login on this one. There are many sites on which I can't shop (can't put things in the basket). Here is an example of that: http://www.damart.co.uk/F-10068-thermal-tops/P-63701--pack-of-2-french-neck -vests Have you tried in safe-mode? Maybe an addon is the culprit. This is pretty standard diagnostic procedure. I haven't got any add-ons in Google Chrome. And the problem exists there. I'll try a different profile before I start removing my one add-on. Which I only recently added, and which hasn't made this problem any worse. It is an on-going problem. Not to mention the fact that Andrei was able to reproduce the second one. This is happening with more and more sites in the UK. I was specifically told by one of them that they don't support earlier versions of Firefox. Which is why I asked about installing a later version of Firefox, rather than trouble shooting. Lisi I'm not a long term Iceweasel user, nor an enthusiastic one. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201406140914.38612.lisi.re...@gmail.com
grub rescue
Hi, Today I tried to install debian from a CD which dated back to 2011. Everything went fine, partition - and then it arrived at the set up the mirror, I just choose default and think later changed in the /etc/apt. It started to download from that default ftp mirror. It was choked there for half a hour, the progress bar didn't proceed and it is said waiting ... The only thing I could do at that time, was took the CD out and reboot. Which I shouldn't have done that. After reboot, it showed me grub rescue when I tried grub rescue ls (hd0, msdos5) error: unknown filesystem. I don't know what I can do next. P.S. Why I choose that old CD because the newly-burned CD failed to enter into the installation. Before the system was Ubuntu. I had freed all space and did the partition. Thanks ahead,
Re: Preseeded setting on openssh-server ignored
On 2014-06-13, Bob Proulx b...@proulx.com wrote: Just to plug a good tool I like using pwgen to generate truly random passwords. A long random password is sufficiently difficult to exploit. If you are using passwords that are easy to crack then they should definitely be disabled. Here is an example: $ pwgen 16 1 au6fiegieCh5shio https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726578 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/slrnlpo3v4.21v.cu...@einstein.electron.org
Re: grub rescue
I choose to reinstall. On Sat, Jun 14, 2014 at 4:40 PM, lina lina.lastn...@gmail.com wrote: Hi, Today I tried to install debian from a CD which dated back to 2011. Everything went fine, partition - and then it arrived at the set up the mirror, I just choose default and think later changed in the /etc/apt. It started to download from that default ftp mirror. It was choked there for half a hour, the progress bar didn't proceed and it is said waiting ... The only thing I could do at that time, was took the CD out and reboot. Which I shouldn't have done that. After reboot, it showed me grub rescue when I tried grub rescue ls (hd0, msdos5) error: unknown filesystem. I don't know what I can do next. P.S. Why I choose that old CD because the newly-burned CD failed to enter into the installation. Before the system was Ubuntu. I had freed all space and did the partition. Thanks ahead,
Re: Listing packages installed from experimental
On Tue, Jun 10, 2014 at 6:41 PM, Javier Barroso javibarr...@gmail.com wrote: El 10/06/2014 02:25, David Glover-Aoki da...@gloveraoki.net escribió: I'm running wheezy but have some packages installed from experimental. How can I list all the packages currently installed from experimental? After having quickly read this thread.. I recommend the new command : apt list | grep experimental apt list --installed | grep experimental -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAOdo=sz7tnw8h919sfrsp7oa-4oafq43mvh-ph4_dmj8q40...@mail.gmail.com
Re: When bug fixes are applied on stable ?
On Thu, Jun 12, 2014 at 4:42 PM, Bob Proulx b...@proulx.com wrote: Prunk Dump wrote: Yes I installed libreoffice-l10n-fr but in libreoffice draw the paper size stay on US letter... Configure the default paper settings with libpaper1. # dpkg-reconfigure libpaper1 That will present a dialog box allowing you to select the default paper size. Because you have a large environment you will probably want to set /etc/papersize directly. (Which is what I do.) The package manages it with ucf. $ cat /etc/papersize IIRC the OP had said that neither locale nor libpaper were setting the paper size to A4 for LO or a component of LO. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAOdo=Sx=1-axjm2tp990bg8sbemqdcqheg2p1xmbc1ksusg...@mail.gmail.com
Re: MPD on localhost won't work if there's no Wifi!?
On Fri 13 Jun 2014 at 15:28:48 -0600, Bob Proulx wrote:
Brian wrote:
Bob Proulx wrote:
Brian wrote:
True. What do think about the lack of '127.0.1.1 localhost' in
It is the 127.0.1.1 localhost to which I was disagreeing. That
would be unusual. It is still the loopback device so off the top of
my head I think everything should still work okay. But for best
compatibilty I think 127.0.0.1 should always be localhost the reverse.
There is quite extensive history attached to the use of 127.0.1.1 in
/etc/hosts. Parts of the most recent discussion is at:
https://lists.debian.org/debian-devel/2013/08/msg00095.html
and
https://lists.debian.org/debian-devel/2013/08/msg00151.html
If the actual hostname of the system is localhost then there is no
need for any other entry other than the 127.0.0.1 entry and the
127.0.1.1 entry isn't needed at all. (Now I need to verify that the
installer doesn't add it in that case. I recall that it does not.)
Teresa had /etc/hostname as localhost. If I do the same d-i writes my
127.0.1.1 line as
127.0.1.1localhost.lan localhost.
during an expert install.
Now that you mentioned the case of what happens if DHCP returns
something unusual I think I would need to check. But I think it still
behaves the same regardless. I don't think anything the DHCP server
returns is going to affect this. But I can't say for certain without
looking and testing. It might.
Not that I have any skills at all in understanding source code but
netcfg has
dhcp.c:if (netcfg_get_hostname(client, netcfg/dhcp_hostname,
interface-dhcp_hostname, 0))
dhcp.c: * If the netcfg/hostname preseed value is set use
that
dhcp.c: * otherwise default to the hostname returned via
DHCP, if any,
dhcp.c: * otherwise to the requested DHCP hostname
dhcp.c: * otherwise to the hostname found in DNS for the IP
address
I am more interested now in what happens in a CD#1 install completely
offline.
The hostname will be either the default (debian) or whatever is
preseeded with hostname= on the command line. I wouldn't expect there to
be a domain name.
dhcp.c:/* We don't have a domain name yet, but we need to write
out the
dhcp.c: * Default to the domain name returned via DHCP, if any
dhcp.c:di_debug(Reading domain name returned via DHCP);
dhcp.c:di_debug(DHCP domain name is '%s', domain);
netcfg-common.c: * Verify that the domain name (or FQDN) conforms to RFC
1123 s2.1, and
netcfg-common.c:} else { /* assume we have a valid domain name
given */
netcfg-common.c:/* Global var 'domain' is holding a temporary
domain name,
Suppose the server doesn't provide a domain name. Then she will have
127.0.1.1 foo
because there is no need for an alias.
That is a good question! But doesn't the installer ask you for a
domain name specifically? I believe it does. Therefore the user
should always enter a domain name. But if they don't then I don't
know what the installer puts there by default.
The default is the domain name returned via DHCP. Blanking the field
results in no domain name.
I _thought_ the installer put the special localdomain string there
in the case that the user left it empty. Because sometimes there
isn't any reasonable thing to put there. In that case it creates a
consistent and valid configuration using localhost and localdomain.
That way applications that require a domain name to be present will
have a constructed one that will work even if bogus. (As I recall
this predates RFC 2606 which created a .localhost domain.)
The idea is that some applications such as Postfix for one example,
along with others, that really want a fully qualified hostname can
have a fully consistent configuration by using localhost.localdomain.
The localdomain part is a created construct. But on an unconnected
system everything can map consistently and everything can work
regardless.
I don't pretend to understand this in its entirety, but from netcfg's
changelog:
[ Thomas Hood ]
* If there is no permanent IP address with which the system hostname
(i.e., that which is returned by the hostname command) can be
associated in /etc/hosts then associate it with address 127.0.1.1
rather than 127.0.0.1. Associating the system hostname with the
latter had the unwanted effect of making 'localhost.localdomain'
the canonical hostname associated with the system hostname.
That is, 'hostname --fqdn' returned 'localhost.localdomain'.
(Closes: #316099)
Programs that access local services at the IP address obtained by
resolving the system hostname SHOULD NOT DO THIS, but those that
do so will not be disappointed: most services that listen locally
listen on all 127/8 addresses, not just on 127.0.0.1
For an expert install the hostname and domain
Re: grub rescue
On Sat, Jun 14, 2014 at 4:40 AM, lina lina.lastn...@gmail.com wrote: Today I tried to install debian from a CD which dated back to 2011. Everything went fine, partition - and then it arrived at the set up the mirror, I just choose default and think later changed in the /etc/apt. It started to download from that default ftp mirror. It was choked there for half a hour, the progress bar didn't proceed and it is said waiting ... The only thing I could do at that time, was took the CD out and reboot. Which I shouldn't have done that. After reboot, it showed me grub rescue when I tried grub rescue ls (hd0, msdos5) error: unknown filesystem. By default, (hd0, msdos5) is a swap partition. You need to run set and ls when you're dropped to a grub rescue prompt in order to determine the set ... commands to run. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAOdo=SwZoWMY9tzZE60YL6pz=z42jq+d1ycayhckjml-66f...@mail.gmail.com
Re: grub rescue
The old NetInstall CD is out of data, that's why it is choked when it tried to grab packages. I burned a new CD with current stable version and it looks fine by far. Thanks, On Sat, Jun 14, 2014 at 6:14 PM, Tom H tomh0...@gmail.com wrote: On Sat, Jun 14, 2014 at 4:40 AM, lina lina.lastn...@gmail.com wrote: Today I tried to install debian from a CD which dated back to 2011. Everything went fine, partition - and then it arrived at the set up the mirror, I just choose default and think later changed in the /etc/apt. It started to download from that default ftp mirror. It was choked there for half a hour, the progress bar didn't proceed and it is said waiting ... The only thing I could do at that time, was took the CD out and reboot. Which I shouldn't have done that. After reboot, it showed me grub rescue when I tried grub rescue ls (hd0, msdos5) error: unknown filesystem. By default, (hd0, msdos5) is a swap partition. You need to run set and ls when you're dropped to a grub rescue prompt in order to determine the set ... commands to run. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAOdo=SwZoWMY9tzZE60YL6pz=z42jq+d1ycayhckjml-66f...@mail.gmail.com
Re: CORRIGENDA - Re: SOLVED: Re: Can Iceweasel and Firefox co-exist on Wheezy.
On 06/14/2014 09:59 AM, Lisi Reisz wrote: deb http://mozilla.debian.net wheezy-backports iceweasel-release I just get into the loop : Thanks for the tip ! Actually I was running both iceweasel and firefox, downsides : 1. can't run them at the same time.. obviously 2. wait for all plugins to be checked and deactivated, each time you start either one Gonna try iceweasel 30.0 right away ! Cheers :) -- “One original thought is worth a thousand mindless quotings.” “Le vrai n'est pas plus sûr que le probable.” Diogene Laerce signature.asc Description: OpenPGP digital signature
Re: Preseeded setting on openssh-server ignored
snip To date I haven't been able to find documented lists of preseeds anywhere, except for the standard debian installer values given in You haven't looked hard enough. Debian's and Ubuntu's example preseed files. I found this preseed option in forum postings somewhere. Which preseed option? You might not be able to find the forum posting but please would you quote this option so we know what you are talking about? I can categorically state there is no preseed option for permit-root-login in Wheezy, Squeeze or Lenny. Can you categorically state what _are_ the preseed options for the openssh-server package? I can find 4: openssh-server ssh/vulnerable_host_keysnote openssh-server ssh/use_old_init_script boolean true openssh-server ssh/encrypted_host_key_but_no_keygennote openssh-server ssh/disable_cr_auth boolean false Do you know of any others? Where are these documented? And while we are at it, are preseed options for each package documented in the package? Cheers Iain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/539c2911.3010...@thargoid.co.uk
Re: grub rescue
On 6/14/14, lina lina.lastn...@gmail.com wrote: Today I tried to install debian from a CD which dated back to 2011. Everything went fine, partition - and then it arrived at the set up the mirror, I just choose default and think later changed in the /etc/apt. It started to download from that default ftp mirror. It was choked there for half a hour, the progress bar didn't proceed and it is said waiting ... The only thing I could do at that time, was took the CD out and reboot. Which I shouldn't have done that. For future reference, you may have been able to change VTs/ Linux consoles, eg: Alt-RightArrow and there you will often see the message press enter to activate console. It's only busybox, so its own learning curve, but has been known to be useful on occasion :) Good luck Zenaan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/caosgnssxto4ma7txgdyvctaoxhyqzrmvf+9kz6s6gwhxvt1...@mail.gmail.com
Re: Preseeded setting on openssh-server ignored
On 06/14/2014 12:57 PM, Lisi Reisz wrote: On Friday 13 June 2014 22:02:06 Bob Proulx wrote: Just to plug a good tool I like using pwgen to generate truly random passwords. A long random password is sufficiently difficult to exploit. If you are using passwords that are easy to crack then they should definitely be disabled. Here is an example: $ pwgen 16 1 au6fiegieCh5shio Can it be set to use anything other than alpha-numeric? If you use lastpass, you have a pretty good password generator to with it, with pronounceable, alpha or not, special characters or not options.. Cheers :) -- “One original thought is worth a thousand mindless quotings.” “Le vrai n'est pas plus sûr que le probable.” Diogene Laerce signature.asc Description: OpenPGP digital signature
[OT] Re: When bug fixes are applied on stable ?
On Sat, 2014-06-14 at 09:30 +1000, Chris Angelico wrote: On Sat, Jun 14, 2014 at 2:06 AM, Chris Bannister cbannis...@slingshot.co.nz wrote: Son: What's a word processor Dad? Dad: Well, you know what a food processor does to food, right? Son: Ah!, I understand. Thanks Dad. Ah! That explains what happened on Ariel when Simon and River were to be taken away for processing. Think River had already been well and truly process before that point. -- Tixy -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1402743857.3959.0.ca...@computer5.home
Re: Preseeded setting on openssh-server ignored
On Friday 13 June 2014 22:02:06 Bob Proulx wrote: Just to plug a good tool I like using pwgen to generate truly random passwords. A long random password is sufficiently difficult to exploit. If you are using passwords that are easy to crack then they should definitely be disabled. Here is an example: $ pwgen 16 1 au6fiegieCh5shio Can it be set to use anything other than alpha-numeric? Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201406141157.59557.lisi.re...@gmail.com
Re: Can Iceweasel and Firefox co-exist on Wheezy.
On 06/14/2014 10:14 AM, Lisi Reisz wrote: On Friday 13 June 2014 19:17:19 Go Linux wrote: On Fri, 6/13/14, Lisi Reisz lisi.re...@gmail.com wrote: Subject: Re: Can Iceweasel and Firefox co-exist on Wheezy. To: debian-user@lists.debian.org Date: Friday, June 13, 2014, 9:01 AM https://beta.ovoenergy.com/login I can't login on this one. There are many sites on which I can't shop (can't put things in the basket). Here is an example of that: http://www.damart.co.uk/F-10068-thermal-tops/P-63701--pack-of-2-french-neck -vests Have you tried in safe-mode? Maybe an addon is the culprit. This is pretty standard diagnostic procedure. I haven't got any add-ons in Google Chrome. And the problem exists there. I'll try a different profile before I start removing my one add-on. Which I only recently added, and which hasn't made this problem any worse. It is an on-going problem. Not to mention the fact that Andrei was able to reproduce the second one. This is happening with more and more sites in the UK. I was specifically told by one of them that they don't support earlier versions of Firefox. Which is why I asked about installing a later version of Firefox, rather than trouble shooting. Lisi I'm not a long term Iceweasel user, nor an enthusiastic one. I went on the damart page with chrome Version 35.0.1916.153, I'm not sure if this your issue but you need to select a quantity to enable the add to basket feature. It worked for me. Good luck ! -- “One original thought is worth a thousand mindless quotings.” “Le vrai n'est pas plus sûr que le probable.” Diogene Laerce signature.asc Description: OpenPGP digital signature
Re: Can Iceweasel and Firefox co-exist on Wheezy.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 06/14/2014 04:14 AM, Lisi Reisz wrote: On Friday 13 June 2014 19:17:19 Go Linux wrote: On Fri, 6/13/14, Lisi Reisz lisi.re...@gmail.com wrote: Subject: Re: Can Iceweasel and Firefox co-exist on Wheezy. To: debian-user@lists.debian.org Date: Friday, June 13, 2014, 9:01 AM https://beta.ovoenergy.com/login I can't login on this one. There are many sites on which I can't shop (can't put things in the basket). Here is an example of that: http://www.damart.co.uk/F-10068-thermal-tops/P-63701--pack-of-2-french-neck -vests Have you tried in safe-mode? Maybe an addon is the culprit. This is pretty standard diagnostic procedure. I haven't got any add-ons in Google Chrome. And the problem exists there. Then... how would it make any sense for this to be an Iceweasel problem? I'll try a different profile before I start removing my one add-on. Which I only recently added, and which hasn't made this problem any worse. It is an on-going problem. Not to mention the fact that Andrei was able to reproduce the second one. If I understand the replies correctly, Andrei's reproduce of the second one was the result of not realizing that in order to enable the add to basket button on that site, you have to select a size first. (As well as allowing the right scripts, if you're blocking any.) With that realization, (s?)he reported that it worked fine in dwb (a Webkit-based browser), though (s?)he didn't retest in Iceweasel since I'd already done that. This is happening with more and more sites in the UK. I was specifically told by one of them that they don't support earlier versions of Firefox. Which is why I asked about installing a later version of Firefox, rather than trouble shooting. Fair enough, but I'd still like to find an example of a site with the problem which I can actually reproduce... if only because I'm likely to be using earlier versions of Firefox (in the form of the ESR release) for the foreseeable future, simply because I don't want to have to jump through the hoops which a did they break anything this time? new-major-version Firefox release requires every six weeks. Speaking of which, if those sites don't support the ESR release of Firefox, they're going to have trouble with a not insignificant part of their potential customer base; they might want to reconsider that. Good luck with newer Iceweasel, with a clean profile, and/or with separate Firefox if you end up going that route. Please report back as to whether any of them do fix anything; I'm particularly interested if they don't. - -- The Wanderer Secrecy is the beginning of tyranny. A government exists to serve its citizens, not to control them. -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCgAGBQJTnDBqAAoJEASpNY00KDJrPYoP/1J4FPLtLuZxQA89uEruBKjH 9vm1A7YlrSCKsizHIiAR28AANase1MElNOEYaXb6TF/ofynCkaUcgO7zgC7m9T7w kvp23tDwQCgbAsDXuyegWRgEmR2h3R2Mp+xbz66cK1PAFRILAaCVJ/huKOQIUUA6 gajIPXjAmMe16PtIEMDhRo0GZl3Q1fDnad+dC54HgQgskjuRxgb6HSAyezNaycus VgzdX9bOlckD+P18kxA4kFJuGfDEs4O5PwaCQvGRd4H1aQiYpfT0SQCGrrsGygvg CuW/vo0V4k4rGJt0oDnNVQLfEBQT1JV0qj4sARGFsbrRtR8cXD6YMoJT6BPLX+x0 ehR9UezcmKldQYk9RZrXb1WXycHOmXXDSNEebCxU8nSQr26pTkMsUGK0Fk40dt+7 vrOvFIWMMvTmwlvEhb5AzYhG4fzWQUCzg/2ZiD0Zcm6oc6pQo95aI8kFuvuSRS2S +DUz9GdUWhdWQjGlsLQsl0kj8TPvSlHeKEkvFbMOGBkwz9VrLz6xhh1/Dv0endOG SYsigzOyZj5UKAiI7NpKl3PphVvBuMFsjOGBkGuvCbqe6X3ZQyzW5x4CfBwDDDoz //nPceUrOeq/wAjMGRKBQNHG1dKTFCGHDfcTsmvXaGTHdnCIIAgtTrabILc33KRA BhldShjfwcnkxC4otJ8U =MGSF -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/539c306a.8020...@fastmail.fm
Re: can't log out and log back in after remove lxde
On 2014-06-14, tom arnall kloro2...@gmail.com wrote: root@debian:/home/tom# which xdm gdm gdm3 kdm lightdm /usr/sbin/lightdm root@debian:/home/tom# Seems you're using the lightdm display manager and that it is not respawning correctly, or at all, when you log out. Maybe if you tried one of the other display managers? Rather than rebooting you might try goin to the console (Ctrl-Alt-F1) and restarting the service (as root) service lightdm restart or service lightdm stop service lightdm start after which you can return to the gui (Alt F7) and hopefully login again. It appears other people have had similar difficulties with lightdm in the past, if I'm understanding correctly the whole deal, which might not be the case. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/slrnlpofff.2db.cu...@einstein.electron.org
Re: Preseeded setting on openssh-server ignored
On Sat 14 Jun 2014 at 11:50:57 +0100, Iain M Conochie wrote: Can you categorically state what _are_ the preseed options for the openssh-server package? I can find 4: The ones you listed below are for a fresh install of Wheezy. Jessie is different. This output can be obtained from debconf-show openssh-server None are prefixed with an '*' so no questions have been asked. openssh-server ssh/vulnerable_host_keysnote openssh-server ssh/use_old_init_script boolean true openssh-server ssh/encrypted_host_key_but_no_keygennote openssh-server ssh/disable_cr_auth boolean false Do you know of any others? Where are these documented? And while we are at it, are preseed options for each package documented in the package? No - except for openssh-server packages which are no longer on the system. debconf-show gives them too. The templates file in a package is as good a place as any to look for preseed options and their documentation. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/14062014134411.bbb315a67...@desktop.copernicus.demon.co.uk
Re: Preseeded setting on openssh-server ignored
On Sat, 14 Jun 2014, Lisi Reisz wrote: Can it be set to use anything other than alpha-numeric? Yes. $ pwgen -sy 16 1; Z/;fv!2B:C=^@kvH If you just want purely random passwords, though, you might try makepasswd instead. pwgen is more biased towards generating distinguishable, memorable passwords instead of truly random ones. -- Don Armstrong http://www.donarmstrong.com It's brief and bright, dear children; bright and brief. Delight's the lightning; the long thunder's grief. -- John Frederick Nims Poetry in Motion p31 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140614170433.go9...@teltox.donarmstrong.com
boot order
Hi all :-) on debian stable I added a script to /etc/init.d/, that script sends an email when the system boot and when the system shutdown I need run that script before that postfix has killed what's the best way to fill: cat /etc/init.d/systememail #!/bin/sh ### BEGIN INIT INFO # Provides: SystemEmail # Required-Start: $remote_fs $syslog $ALL # Required-Stop: $syslog # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: Send email [...] normally after created a script I do: insserv /etc/init.d/name_of_script thanks for help! Pol -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/539c8fe5.9000...@fuckaround.org
Re: Iceweasel problem
On Fri, Jun 13, 2014 at 07:25:37PM -0700, Bob Holtzman wrote: On Fri, Jun 13, 2014 at 01:02:36PM -0400, Steve Litt wrote: On Thu, 12 Jun 2014 13:06:55 -0700 Bob Holtzman hol...@cox.net wrote: Running updated Wheezy w/ Iceweasel 24.5.0 on a Thinkpad 420i. Every time I start the computer from a shutdown or wake it from hibernation Iceweasel opens and I close it 6 consecutive times in rapid succession. After the 6th time it stays closed unless I deliberately open it. Online searches have been no help. As a matter of fact, I couldn't find one mention of the problem. Maybe I missed it. Any pointers would be appreciated. Make a new user called junk (or junk2 if you already have user junk), and see if the problem occurs with user junk. Whether it does or it doesn't, either way it will give you valuable insight into narrowing the root cause scope. Steve, Thanks for the reply. As sometimes happens, the machine seems to have cured itself with no intervention on my part. I wish I knew what went on. Sorry for the noise. Looks like I spoke too soon. The problem is back this morning. It appears that it will continue on an intermittent basis. Steve, I'll try your suggestion as soon as I have time. -- Bob Holtzman A man is a man who will fight with a sword or tackle Mt Everest in snow, but the bravest of all owns a '34 Ford and tries for 6000 in low. signature.asc Description: Digital signature
Re: Preseeded setting on openssh-server ignored
Don Armstrong wrote, On 06/14/2014 01:04 PM: If you just want purely random passwords, though, you might try makepasswd instead. pwgen is more biased towards generating distinguishable, memorable passwords instead of truly random ones. Here's a way to generate a *truly* random password that is *also* memorable: http://diceware.com Instead of using your computer to generate allegedly random bits, you use five six-sided dice to generate truly random bits. -- Patrick -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/539c8f30.8070...@rayservers.net
Re: Preseeded setting on openssh-server ignored
On Sat, 14 Jun 2014 14:06:40 -0400 Patrick Chkoreff patr...@rayservers.net wrote: Instead of using your computer to generate allegedly random bits, you use five six-sided dice to generate truly random bits. You can also eat peas and count the number of seconds between two farts, then divide it by the captain's age. Ok, I -[] -- Chess Hey guys, I've got a pure idea ! *aX1s play dead *Deadpool put his head in the microwave *Qwerty jump by the window *Landlord dig an evasion tunnel in the floor *Arg`tr gulp down a Prozac tube *Planetary make himself hara-kiri with a tea spoon Chess :'( signature.asc Description: PGP signature
Re: boot order
On Sat 14 Jun 2014 at 20:09:41 +0200, Pol Hallen wrote: on debian stable I added a script to /etc/init.d/, that script sends an email when the system boot and when the system shutdown But you are are not going to show this script to us. It is a secret. so we do not know whether it is a viable, working script. You may know but you do not tell us. If you did, the tweaking may be worth the effort. I need run that script before that postfix has killed what's the best way to fill: cat /etc/init.d/systememail #!/bin/sh ### BEGIN INIT INFO # Provides: SystemEmail # Required-Start: $remote_fs $syslog $ALL # Required-Stop: $syslog # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: Send email [...] Ah, this is it; you want someone to write a script from scratch for you. You provide the well known stock headers. We do the work. normally after created a script I do: insserv /etc/init.d/name_of_script That's nice to know. You get to do a little bit of work. You might want to look at @reboot with cron for the startup. Don't say I didn't help you. Now for something completely off-topic: The domain for your email address is naff. It marks you out as being someone who doesn't mind being regarded as a plonker. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140614191608.gb17...@copernicus.demon.co.uk
Re: boot order
On Sat, 14 Jun 2014 20:16:08 +0100 Brian a...@cityscape.co.uk wrote: You might want to look at @reboot with cron for the startup. Don't say I didn't help you. Not to mention there are tons of howtos about this matter on the web, as it is the most basic of monitoring… -- @rondoudou hi, somebody want to cook for me, pls? @Asone Order a chinese @Corsac Asone: slavery was abolished long ago… signature.asc Description: PGP signature
Re: Preseeded setting on openssh-server ignored
Curt wrote: Bob Proulx wrote: Just to plug a good tool I like using pwgen to generate truly random passwords. A long random password is sufficiently difficult to exploit. If you are using passwords that are easy to crack then they should definitely be disabled. Here is an example: $ pwgen 16 1 au6fiegieCh5shio https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726578 That ticket is mostly an argument over defaults. But you are right that the way I am using it and proposing it to others I should add the -s option. Instead of: $ pwgen 16 1 shohReeg3ceidae7 That should at least have -s instead: $ pwgen -s 16 1 pfqePLprEjMy9D3s However at 16 characters or more even the default options still provide quite a bit of entropy and would be hard to exploit. The biggest problem I have found using random passwords is that some sites truncate the password to a shorter number of characters. Some of those are fairly high profile sites! http://www.schwab.com/ is a good example that truncates passwords at eight characters. There is no defensible rationale for doing that truncation. When I see that I assume that means that they are storing the plaintext of the password somewhere. Otherwise if they were properly hashing the password why would they feel the need to truncate it? Bob signature.asc Description: Digital signature
Re: boot order
But you are are not going to show this script to us.
:-) See at the end of email
You might want to look at @reboot with cron for the startup.
thanks :-)
The domain for your email address is
[...]
domain (mine) of email (mine) is not your problem and if you don't like
it's not my problem ;-)
here the script (rearrange) for debian
bye
Pol
EMAIL=root
RESTARTSUBJECT=[`hostname` `date`] – System Startup
SHUTDOWNSUBJECT=[`hostname` `date`] – System Shutdown
RESTARTBODY=This is an automated message to notify you that
`hostname` started successfully. Start up Date and Time: `date`
SHUTDOWNBODY=This is an automated message to notify you that
`hostname` is shutting down. Shutdown Date and Time: `date`
LOCKFILE=/var/lock/SystemEmail
RETVAL=0
# Source function library.
. /lib/lsb/init-functions
stop()
{
echo -n Sending Shutdown Email:
echo ${SHUTDOWNBODY} | mail -s ${SHUTDOWNSUBJECT} ${EMAIL}
sleep 4
RETVAL=$?
sleep 4
if [ ${RETVAL} -eq 0 ]; then
rm -f ${LOCKFILE}
sleep 4
log_success_msg
else
log_failure_msg
fi
echo
return ${RETVAL}
}
start()
{
echo -n Sending Startup Email:
echo ${RESTARTBODY} | mail -s ${RESTARTSUBJECT} ${EMAIL}
RETVAL=$?
if [ ${RETVAL} -eq 0 ]; then
touch ${LOCKFILE}
log_success_msg
else
log_failure_msg
fi
echo
return ${RETVAL}
}
case $1 in
start)
start
;;
stop)
stop
;;
status)
echo Not applied to service
;;
restart)
stop
start
;;
reload)
echo Not applied to service
;;
condrestart)
#
echo Not applied to service
;;
probe)
;;
*)
echo Usage: SystemEmail{start|stop|status|reload|restart[|probe]
exit 1
;;
esac
exit ${RETVAL}
--
Pol
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/539cba69.1070...@fuckaround.org
Re: Resizing LVM issue
On 06/05/2014 11:29 AM, Jochen Spieker wrote: Miroslav Skoric: On 06/01/2014 11:36 PM, Jochen Spieker wrote: If you don't have a backup you can try to resize the LV again to its original size and hope for the best. Thanks for suggestions. Yep, I managed to return back to the original size at first. Then I resized it properly (incl. leaving few gigs as unused space). e2fsck did spent a while to recheck each partition but seems that everything is in order now. We'll see in days to come ... Nice! It is still possible that some of your data was overwritten but if the fsck didn't find anything troubling you are probably safe now. Next todo: implement a useful backup strategy. :) J. Just to let you know that after some ten days after 2nd resizing everything is still in order (no complaints from fsck or else). From the lesson learned: The proper order of commands should be carefully performed; In that case, resizing the LVM is a good option until the installation process improves itself in a way it automatically format new partitions to be better balanced. (I mean, if I remember properly, during the initial system installation some years ago ... it was 6.0.1a that I upgraded to 7.5 since ... it offered to setup the LVM partitions automatically. So I accepted its recommendation.) But recently I realized that I needed more space in /tmp and found that I had more than enough free space in /home ... that was the reason for resizing. (Btw, the app apt-on-CD recently started to ask for more space in /tmp. After resizing, that app seems to be happy :-) M. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/539cc5ec.30...@eunet.rs
Re: Resizing LVM issue
On 06/05/2014 11:04 AM, Bob Proulx wrote:
Richard Hector wrote:
I prefer not to get in the situation where I have to shrink a filesystem
though - xfs doesn't support it anyway.
Agreed. Even better is to avoid it. Small ext{3,4} file systems
shrink acceptably well. But larger ext{3,4} file systems can take a
very long time to shrink. I once made the mistake of trying to shrink
a 600G filesystem. The operation was eventually successful. But it
took 10 days to complete! And once I started it there was no other
option than to let it complete.
Two questions:
1. What would you do if you need more space in /tmp and you know you
have some spare space in /home or else, but do not want to reinstall?
2. Wouldn't be nice if resizing routines/commands/programs/... show
calculated time they would need for such an operation, so a user could
decide whether to continue or cancel?
M.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/539cc14a.3010...@eunet.rs
Re: Resizing LVM issue
On 06/05/2014 08:42 AM, Richard Hector wrote: If I have to shrink a filesystem, I tend to shrink it to something smaller than my eventual goal, then shrink the LV to the goal, then resize2fs again without specifying the size, so it grows to fit. I prefer not to get in the situation where I have to shrink a filesystem though - xfs doesn't support it anyway. Richard Thanks for suggestions. Well I would not shrink the filesystem (actually a part of it) if I did not need more space on /tmp (as a part of the LVM). Anyway, after this experience, may I suggest to LVM programmers to think about some software routines that would enable users to recompose (resize, shrink, whatever ...) their LVM from within a mounted system, in a way that after the next reboot, the LVM and FS automatically recomposes itself - so to avoid common mistakes. M. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/539cbfa4.7060...@eunet.rs
Re: Resizing LVM issue
On Sat, 14 Jun 2014 23:40:26 +0200 Miroslav Skoric sko...@eunet.rs wrote: 1. What would you do if you need more space in /tmp and you know you have some spare space in /home or else, but do not want to reinstall? http://www.yourhowto.net/increase-tmp-partition-size-linux/ However, adding some GB of RAM would be better (to extend tmpfs). 2. Wouldn't be nice if resizing routines/commands/programs/... show calculated time they would need for such an operation, so a user could decide whether to continue or cancel? This would be only be empiric (or take a huge algorithm and a lot of CPU/RAM to correctly compute). -- ju the Lord does not touch many people nowadays fab priests take care of this for him signature.asc Description: PGP signature
Re: boot order
On Saturday 14 June 2014 22:11:05 Pol Hallen wrote: domain (mine) of email (mine) is not your problem and if you don't like it's not my problem ;-) No, but if all of us decide not to like it, and kill-file you as I am now doing, it might become your problem if you wanted help. Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201406142320.28521.lisi.re...@gmail.com
Re: Resizing LVM issue
On 6/14/2014 4:33 PM, Miroslav Skoric wrote: ...may I suggest to LVM programmers to think about some software routines that would enable users to recompose (resize, shrink, whatever ...) their LVM from within a mounted system, in a way that after the next reboot, the LVM and FS automatically recomposes itself - so to avoid common mistakes. This is not possible. A filesystem must be shrunk before the underlying storage device. If you shrink the LV first then portions of the filesystem will now map to non-existent sectors. If files exist in those sectors they will be lost. Same goes for filesystem metadata. It is possible to add sectors to a device under a mounted filesystem because the filesystem has no knowledge of them, and is not mapping them. The same is not true of removing sectors under a mounted filesystem, for the reason above. Cheers, Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/539cd28a.20...@hardwarefreak.com
logrotate cannot rotate some log files
Hello debianers!
I recently noticed that some log files on a wheezy box are not being
rotated anymore and are getting rather large. I went through
logrotate.conf and logrotate.d and did not spot anything wrong. When I
run logrotate -f -v /etc/logrotate.conf, some error messages are shown,
but they are not quite helpful in solving the issue.
For example, /var/log/syslog:
#ls -lsh /var/log/syslog
1.2G -rw-r- 1 root adm 1.2G Jun 14 21:33 /var/log/syslog
# cat /etc/logrotate.d/rsyslog
/var/log/syslog
{
rotate 7
daily
missingok
notifempty
delaycompress
compress
postrotate
invoke-rc.d rsyslog rotate /dev/null
endscript
}
# logrotate -f -v /etc/logrotate.d/ 2 logrotate.txt
# cat logrotate.txt | grep syslog
reading config file rsyslog
rotating pattern: /var/log/syslog
considering log /var/log/syslog
rotating log /var/log/syslog, log-rotateCount is 7
error: error creating output file /var/log/syslog.1.gz: File exists
log /var/log/syslog.8.gz doesn't exist -- won't try to dispose of it
# ls -lsh /var/log/syslog.1.gz
0 -rw-r- 1 root adm 0 Feb 9 07:35 /var/log/syslog.1.gz
# ls -lsh /var/log/syslog.1
3.8M -rw-r- 1 root adm 3.8M Feb 8 07:35 /var/log/syslog.1
So this issue appears to go back some months already, but I have no clue
why it started. Also, it does no happen to every log file on /var/log,
just some, eg., messages, debug, kern.log, auth.log.
Could someone please give a hint on how might I solve this issue?
Thanks!
--
André N. Batista
GNUPG/PGP KEY: 6722CF80
signature.asc
Description: This is a digitally signed message part
Re: logrotate cannot rotate some log files
On Sat, 14 Jun 2014 21:49:35 -0300 André Nunes Batista andrenbati...@gmail.com wrote: 0 -rw-r- 1 root adm 0 Feb 9 07:35 /var/log/syslog.1.gz Move out syslog* to another place and restart syslog (looks like you have a hole in file numbering). If that doesn't work, try to reinstall logrotate and rsyslog (or switch to syslog-ng). -- thithi And you, who knows you best? fred my mother bgdu60 my girlfriend :) isis uuh... my sister I guess tercalen google... signature.asc Description: PGP signature
Re: Resizing LVM issue
Miroslav Skoric: Two questions: 1. What would you do if you need more space in /tmp and you know you have some spare space in /home or else, but do not want to reinstall? If it's only temporarily, I would probably do a bind-mount. Just create ~/tmp-tmp, as root cp -a /tmp ~/tmp-tmp/, mount -o bind ~/tmp-tmp/tmp /tmp. (Sorry for the many tmps. :)) But I never had that issue in several years running sid on a laptop with 4GB RAM and /tmp as tmpfs. 2. Wouldn't be nice if resizing routines/commands/programs/... show calculated time they would need for such an operation, so a user could decide whether to continue or cancel? They would do that if there was a way to know in advance. I don't think it's possible to do more than a wild guess which I assume could still be off by a factor of two or more. J. -- When standing at the top of beachy head I find the rocks below very attractive. [Agree] [Disagree] http://www.slowlydownward.com/NODATA/data_enter2.html signature.asc Description: Digital signature
Re: Preseeded setting on openssh-server ignored
On 6/14/2014 2:06 PM, Patrick Chkoreff wrote: Don Armstrong wrote, On 06/14/2014 01:04 PM: If you just want purely random passwords, though, you might try makepasswd instead. pwgen is more biased towards generating distinguishable, memorable passwords instead of truly random ones. Here's a way to generate a *truly* random password that is *also* memorable: http://diceware.com Instead of using your computer to generate allegedly random bits, you use five six-sided dice to generate truly random bits. -- Patrick Not good at all. With 5 dice, you have 6^5 or 7,776 possible combinations. Just figuring 5 upper and lower case characters and numbers, you have 62^5 or 916,132,832 (more if you add special characters). Even a 3 alphanumeric (upper and lower) case character password has 238,328 possible combinations. I wouldn't even consider this a weak password. It's much worse than that. The fact you can have combinations of words doesn't add that much security, especially if someone thinks you're using the diceware list. Jerry -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/539d05b0.5050...@attglobal.net
Off-topic: boot order
On Sat, 2014-06-14 at 23:20 +0100, Lisi Reisz wrote: On Saturday 14 June 2014 22:11:05 Pol Hallen wrote: domain (mine) of email (mine) is not your problem and if you don't like it's not my problem ;-) No, but if all of us decide not to like it, and kill-file you as I am now doing, it might become your problem if you wanted help. Lisi tends to write off-topic mails to Debian user instead to write off-list, especially if she let us know, that she again kill-filed somebody. I guess it would cause Lisi less work, if she would block all mails and to add exceptions for addresses that she wants to receive. However an English to German dictionary mentions, that the OP's address is vulgarly for get up to nonsense and similar, the Urban dictionary mentions this too and mentions the meaning of open sexually, so it seems not really to offend the Debian Code of Conduct, Version 1.0 ratified on April 28th, 2014. It likely depends to the kind of the colorful language. Since the vocabulary used for the OP's address is less vulgarly, less obscenely than lyrics of common English radio and TV songs in the daytime, I guess we should Assume good faith and keep in mind that many of our Contributors are not native English speakers or may have different cultural backgrounds. Regards, Ralf -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1402803899.3692.40.camel@archlinux
Re: Preseeded setting on openssh-server ignored
On Sat, 14 Jun 2014, Bob Proulx wrote: The biggest problem I have found using random passwords is that some sites truncate the password to a shorter number of characters. Some of those are fairly high profile sites! http://www.schwab.com/ is a good example that truncates passwords at eight characters. There is no defensible rationale for doing that truncation. When I see that I assume that means that they are storing the plaintext of the password somewhere. Otherwise if they were properly hashing the password why would they feel the need to truncate it? well, this doesn't look all that old... http://docs.oracle.com/cd/E18752_01/html/816-4558/toc.html The System Administration Guide: Naming and Directory Services (NIS+) Copyright © 1994, 2010, Oracle and/or its affiliates. All rights reserved. and, drilling down a little... http://docs.oracle.com/cd/E18752_01/html/816-4558/a08paswd-15680.html A password must meet the following requirements: * Length. By default, a password must have at least six characters. Only the first eight characters are significant. (In other words, you can have a password that is longer than eight characters, but the system only checks the first eight.) Because the minimum length of a password can be changed by a system administrator, it may be different on your system. pretty nice, eh? there is an NIS package in debian. couldn't find any indication of its maximum (significant) password length, myself. does it check more than eight characters? -wes
Re: logrotate cannot rotate some log files
On 15/06/2014 10:49 AM, André Nunes Batista wrote: # logrotate -f -v /etc/logrotate.d/ 2 logrotate.txt # cat logrotate.txt | grep syslog reading config file rsyslog rotating pattern: /var/log/syslog considering log /var/log/syslog rotating log /var/log/syslog, log-rotateCount is 7 error: error creating output file /var/log/syslog.1.gz: File exists log /var/log/syslog.8.gz doesn't exist -- won't try to dispose of it # ls -lsh /var/log/syslog.1.gz 0 -rw-r- 1 root adm 0 Feb 9 07:35 /var/log/syslog.1.gz # ls -lsh /var/log/syslog.1 3.8M -rw-r- 1 root adm 3.8M Feb 8 07:35 /var/log/syslog.1 So this issue appears to go back some months already, but I have no clue why it started. Also, it does no happen to every log file on /var/log, just some, eg., messages, debug, kern.log, auth.log. It may have happened when logrotate tried to run twice on the same day. The easiest thing to do is to rename the /old/ problem files (or move them) and then try again to do a logrotate. Cheers A. signature.asc Description: OpenPGP digital signature
Re: boot order
hi.
EMAIL=root
RESTARTSUBJECT=[`hostname` `date`] – System Startup
SHUTDOWNSUBJECT=[`hostname` `date`] – System Shutdown
RESTARTBODY=This is an automated message to notify you that `hostname`
started successfully. Start up Date and Time: `date`
SHUTDOWNBODY=This is an automated message to notify you that `hostname` is
shutting down. Shutdown Date and Time: `date`
LOCKFILE=/var/lock/SystemEmail
RETVAL=0
# Source function library.
. /lib/lsb/init-functions
stop()
{
echo -n Sending Shutdown Email:
echo ${SHUTDOWNBODY} | mail -s ${SHUTDOWNSUBJECT} ${EMAIL}
sleep 4
RETVAL=$?
sleep 4
i can't comment on the rest of the script, but you probably want
RETVAL to be the exit status of the pipeline that sends the mail.
making RETVAL the exit status of 'sleep 4' looks wrong to me.
maybe the author was trying to tell themself to get more sleep?
if [ ${RETVAL} -eq 0 ]; then
rm -f ${LOCKFILE}
sleep 4
log_success_msg
else
log_failure_msg
fi
[--more--]
-wes
