April 2009 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Edit a file with gedit as root causes error messages
by buzlite 29 Apr '09

29 Apr '09

When I su to root to edit a text file, I received the following message in the console. Could someone give some insight? Thanks $ su Password: # gedit /etc/wvdial.conf (gedit:4437): EggSMClient-WARNING **: Failed to connect to the session manager: None of the authentication protocols specified are supported GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) # -- View this message in context: http://www.nabble.com/Edit-a-file-with-gedit-as-root-causes-error-messages-… Sent from the openSUSE community mailing list archive at Nabble.com. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

3 3

[opensuse] Re: gnome gui startup error message
by Joachim Schrod 29 Apr '09

29 Apr '09

buzlite wrote: > When I reboot my opensuse 11.1, using the Gnome gui. A dialog box would > appear saying: > > Could not update ICEauthority file /home/someuser/.ICEauthority Does the file exist and is owned by a different user than someuser? If yes, delete it. I had this error the last time when I called k3b from a remote system with sudo. The ownership of ~/.ICEauthority got changed to root and the next application could not open it, access rights being 600. Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod(a)acm.org Roedermark, Germany -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 1

[opensuse] gnome gui startup error message
by buzlite 28 Apr '09

28 Apr '09

When I reboot my opensuse 11.1, using the Gnome gui. A dialog box would appear saying: Could not update ICEauthority file /home/someuser/.ICEauthority Could some one help out? Thanks -- View this message in context: http://www.nabble.com/gnome-gui-startup-error-message-tp23283983p23283983.h… Sent from the openSUSE community mailing list archive at Nabble.com. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 1

[opensuse] proftp to pure-ftp
by James D. Parra 28 Apr '09

28 Apr '09

Hello, I have proftp set up on Suse 9.3 machine and it has worked out great for me over the years. However, I need to move my ftp data to a Suse 11.0 server and was curious as to anyone's familiarity with pure-ftp and if there would be any difficulties in migrating to a new ftp service. Many thanks in advance. James -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] Parse error when adding repository security/openSUSE_10.3
by Wilfred van Velzen 28 Apr '09

28 Apr '09

I want to add: http://download.opensuse.org/repositories/security/openSUSE_10.3/ To the repositories I use on an openSUSE 10.3 server. But when I do I'm getting the following error when I choose 'Software Management' in Yast. "There was an error in the repository initialization. 'openSUSE_10.3': Parse error" How do I fix this? Met vriendelijke groet / Best regards, Wilfred van Velzen -- SERCOM Regeltechniek b.v. Heereweg 9 2161 AB Lisse Nederland +31 (0)252 416530 (voice) +31 (0)252 419481 (fax) <http://www.sercom.nl/> Op al onze offertes, op alle opdrachten aan ons en op alle met ons gesloten overeenkomsten zijn toepasselijk de METAALUNIEVOORWAARDEN, gedeponeerd ter Griffie van de Rechtbank te Rotterdam, zoals deze luiden volgens de laatstelijk aldaar neergelegde tekst. De leveringsvoorwaarden worden u op verzoek toegezonden. --- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 1

[opensuse] Re: Curiosity really can kill -- or at least slow you down quite a bit...
by Joachim Schrod 28 Apr '09

28 Apr '09

David C. Rankin wrote: > Joachim Schrod wrote: >> David C. Rankin wrote: >>> Listmates, >>> >>> >>> for i in $(find /proc/24214 -type f); do echo -e "$i\t$(cat $i)"; done >> >> Actually, writing this shell command that way is *never* good >> style. You expand the output of a command into a shell string just >> to output it. That's nonsensical, you might just echo -n your tab >> and then call cat. (Both -e and -n are bashisms, btw, and are not >> necessarily portable to other shells. From my quotes file, a Usenet >> snippet from Larry Wall: >> >> ------------- >> Drew Mills writes: >> : A contest to see who could write the most useful script that could >> : actually be used in the most languages *as is* [...] >> >> I've written some scripts that work in 582 different languages, >> all of them named sh. >> ------------- >> ) >> >> Joachim >> > > I used the expansion because I knew the number of files wasn't a concern. I > know I could have just used -print0 | xargs -0 echo 'bla bla...'; and in hind > site, it would have been better, but I don't think it made any difference in > this case because the number of files was just about 100. As for the -e > bashisms, call me lazy but I just wanted to put a quick tab in between the file > name and its contents. David, that was not my point. The for loop is completely fine for the task at hand. I wanted to point out that echo -e "$i\t$(cat $i)" is dangerous, should better be avoided, and written as echo -n "$i\t" ; cat $i That way you don't slurp the whole content of $i (several megs, maybe gigs if you would start a directory above), just to get a shell string where you prepend some bytes -- doubling the memory usage at this time -- to get a new string that is finally just output. You can let cat do the output itself, no need to capture it first. Please don't take this as a critic; just a tip, how approx. the same amount of chars results in a better script... :-) Cheers, Joachim [writing shell scripts since 1982... ;-)] -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod(a)acm.org Roedermark, Germany -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

Re: [opensuse] list settings wrong
by Carl Spitzer 28 Apr '09

28 Apr '09

Here is a full header showing the loss of the authors email address which makes a proper reply impossible. the backup email addresses do not have this problem. CWSIV X-Auth-No: Return-Path: <opensuse+bounces-88397-cwsiv=myrealbox.com(a)opensuse.org> Received: from myrealbox.com not authenticated [10.1.1.16] by gateway.myrealbox.com with NetMail SMTP Agent $Revision: 12942 $ on Linux; Sun, 26 Apr 2009 19:58:17 -0600 Received: from lists4.suse.de (localhost [127.0.0.1]) by lists4.suse.de (Postfix) with SMTP id 8A49A6C0D23; Sun, 26 Apr 2009 15:07:22 +0000 (GMT) X-Original-To: opensuse(a)lists4.opensuse.org Delivered-To: opensuse(a)lists4.opensuse.org Received: from Relay2.suse.de (relay2.suse.de [149.44.160.89]) by lists4.suse.de (Postfix) with ESMTP id 810AF6C08B7 for <opensuse(a)lists4.opensuse.org>; Sun, 26 Apr 2009 15:07:21 +0000 (GMT) Received: from relay2.suse.de (localhost [127.0.0.1]) by Relay2.suse.de (Postfix) with ESMTP id 482EF3405160 for <opensuse(a)lists4.opensuse.org>; Sun, 26 Apr 2009 17:08:29 +0200 (CEST) X-Virus-Scanned: by amavisd-new at relay2.suse.de X-Spam-Score: -4.6 X-Spam-Level: X-Spam-Status: No, score=-4.6 tagged_above=-20 required=5 tests=[BAYES_00=-2.599, MY_LINUX=-1, MY_SUSE=-1, SPF_PASS=-0.001] Received: from mx2.suse.de ([195.135.220.15]) by relay2.suse.de (relay2.suse.de [149.44.160.89]) (amavisd-new, port 10025) with ESMTP id 8DQiqlmFvf6D for <opensuse(a)lists4.opensuse.org>; Sun, 26 Apr 2009 17:08:23 +0200 (CEST) Received: from ctsmtpout2.frontal.correo (outmailhost.telefonica.net [213.4.149.242]) by mx2.suse.de (Postfix) with ESMTP id A366586391 for <opensuse(a)opensuse.org>; Sun, 26 Apr 2009 17:08:22 +0200 (CEST) Received: from nimrodel.valinor (88.23.230.230) by ctsmtpout2.frontal.correo (7.2.056.6) (authenticated as cerobin.jobs) id 49EA5FC0001623A2 for opensuse(a)opensuse.org; Sun, 26 Apr 2009 17:08:20 +0200 Received: from localhost (localhost [127.0.0.1]) by nimrodel.valinor (Postfix) with ESMTP id CE2C6B6ACB for <opensuse(a)opensuse.org>; Sun, 26 Apr 2009 17:08:18 +0200 (CEST) Received: from nimrodel.valinor ([127.0.0.1]) by localhost (nimrodel.valinor [127.0.0.1]) (amavisd-new, port 10024) with LMTP id mwJt9XTpuqJ3 for <opensuse(a)opensuse.org>; Sun, 26 Apr 2009 17:08:18 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by nimrodel.valinor (Postfix) with ESMTP id 55D95B6AC2 for <opensuse(a)opensuse.org>; Sun, 26 Apr 2009 17:08:18 +0200 (CEST) Date: Sun, 26 Apr 2009 17:08:09 +0200 (CEST) From: opensuse+bounces-88397-cwsiv=myrealbox.com(a)opensuse.org X-X-Sender: cer(a)nimrodel.valinor To: OS-en <opensuse(a)opensuse.org> Subject: Re: [opensuse] keep alive SSH tunnel after resume In-Reply-To: <87f94c370904260655k172bff39udb2f57c309e09952(a)mail.gmail.com> Message-ID: <alpine.LSU.2.00.0904261706280.4850(a)nimrodel.valinor> References: <200904261150.10383.p1037905(a)gmail.com> <87f94c370904260655k172bff39udb2f57c309e09952(a)mail.gmail.com> User-Agent: Alpine 2.00 (LSU 1167 2008-08-23) Precedence: bulk Mailing-List: contact opensuse+help(a)opensuse.org; run by mlmmj X-Mailinglist: opensuse List-Post: <mailto:opensuse@opensuse.org> List-Help: <mailto:opensuse+help@opensuse.org> List-Subscribe: <mailto:opensuse+subscribe@opensuse.org> List-Unsubscribe: <mailto:opensuse+unsubscribe@opensuse.org> List-Owner: <mailto:opensuse+owner@opensuse.org> List-Archive: <http://lists.opensuse.org/opensuse/> X-MIME-Notice: attachments may have been removed from this message MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Evolution-Source: pop://cwsiv@pop3.myrealbox.com/ -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sat, 2009-04-25 at 02:46 -0500, Boyd Stephen Smith Jr. wrote: > In <1240640132.25129.4.camel(a)linux.site>, Carl Spitzer wrote: > >On Fri, 2009-04-24 at 19:21 -0500, opensuse > >+bounces-88292-cwsiv=myrealbox.com(a)opensuse.org > > > >In place of the authors email I get this opensuse+bounces nonsense. > >H0w can this be corrected on the OpenSuSE.org server. > > It can't. You are using the wrong header. > > The "From" header is unmodified by the list software and should contain the > author's address -- or whatever address the author chose to show. > > The "Return-Path" header is replaced or added by the list software and > contains the address to send MDNs and other automated replies so they can be > handled by the list software (e.g. by retrying the message at a later time, > removing a user from the list, or turning off mail delivery to a user > temporarily). > > You were a bit terse with your query. If I've answered the wrong question, > reply rephrase your query and include more detail. If you still assert the > list headers are incorrectly formated, please provide more evidence to back up > your assertion. -- _______ _______ _______ __ / ____\ \ / / ____|_ _\ \ / / | | \ \ /\ / / (___ | | \ \ / / | | \ \/ \/ / \___ \ | | \ \/ / | |____ \ /\ / ____) |_| |_ \ / \_____| \/ \/ |_____/|_____| \/ | \ /|\ || |\ / |~~\ /~~\ /~~| //~~\ | \ / | \ || | X |__/| || |( `--. |__ | | \| \_/ / \ | \ \__/ \__| \\__/ -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

5 4

[opensuse] Re: Curiosity really can kill -- or at least slow you down quite a bit...
by Joachim Schrod 28 Apr '09

28 Apr '09

David C. Rankin wrote: > Listmates, > > A caution to the curious. Never.. Ever... use a for loop and cat to attempt to > look at *all* the values for a process in /proc. Bad things happen on 11.0 > (probably all versions). > > I wanted to look at the values for a bash shell running in konsole as process > 24214 so I did: > > for i in $(find /proc/24214 -type f); do echo -e "$i\t$(cat $i)"; done > > The system slowed to a crawl... There are binary files below /proc. Some of them may produce very long output, e.g., pagemap on my system is 26MB long, which surely would break my terminal. It's typically not a good idea to output them with cat & echo. Actually, writing this shell command that way is *never* good style. You expand the output of a command into a shell string just to output it. That's nonsensical, you might just echo -n your tab and then call cat. (Both -e and -n are bashisms, btw, and are not necessarily portable to other shells. From my quotes file, a Usenet snippet from Larry Wall: ------------- Drew Mills writes: : A contest to see who could write the most useful script that could : actually be used in the most languages *as is* [...] I've written some scripts that work in 582 different languages, all of them named sh. ------------- ) Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod(a)acm.org Roedermark, Germany -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 1

[opensuse] openSUSE 11.0: Automount: unexpected pthreads error: 16 at 523 in indirect.c
by Bernd Nies 28 Apr '09

28 Apr '09

Hi, We have openSUSE 11.0 with the latest patch level and using NFS automounter with user, group and automount entries in LDAP. Since a patch update some 2-3 weeks agou the automounter dies frequently. Are there other victims of this bug who have found a better fix than starting automount manually? /var/log/messages ----------------- Apr 27 09:27:29 adnwsbe09 automount[3753]: lookup_mount: lookup(ldap): key ".Trash-3114" not found in map Apr 27 09:27:29 adnwsbe09 automount[3753]: lookup_mount: lookup(ldap): key ".Trash" not found in map Apr 27 09:27:29 adnwsbe09 automount[3753]: lookup_mount: lookup(ldap): key ".Trash-3114" not found in map Apr 27 09:27:29 adnwsbe09 automount[3753]: unexpected pthreads error: 16 at 523 in indirect.c System info ----------- adnwsbe09:~ # uname -a Linux adnwsbe09 2.6.25.20-0.1-pae #1 SMP 2008-12-12 20:30:38 +0100 i686 i686 i386 GNU/Linux adnwsbe09:~ # rpm -q autofs autofs-5.0.3-40.1 Automounter Config ------------------ adnwsbe09:~ # cat /etc/auto.master /home ldap nismapname=auto_home,ou=be,dc=example,dc=com /homezh ldap nismapname=auto_home,ou=zh,dc=example,dc=com /share ldap nismapname=auto_share_linux,ou=be,dc=example,dc=com adnwsbe09:~ # cat /etc/nsswitch.conf passwd: files ldap group: files ldap hosts: files dns networks: files services: files protocols: files rpc: files ethers: files netmasks: files netgroup: files ldap publickey: files bootparams: files automount: files ldap aliases: files adnwsbe09:~ # cat /etc/ldap.conf uri ldaps://ldap-net7.example.com:636 ldaps://ldap-net12.example.com:636 ldaps://ldap-net5.example.com:636 base ou=be,dc=example,dc=com scope one ldap_version 3 ssl on tls_reqcert never tls_checkpeer no tls_crlcheck none binddn cn=proxyagent,ou=special_users,dc=example,dc=com bindpw ************ debug 0 timelimit 30 bind_timelimit 30 bind_policy soft idle_timelimit 60 pam_lookup_policy yes pam_password exop nss_initgroups_ignoreusers root,ldap nss_schema rfc2307bis nss_map_attribute uniqueMember member nss_base_passwd ou=people,dc=example,dc=com nss_base_shadow ou=people,dc=example,dc=com nss_base_group ou=group,dc=example,dc=com nss_base_hosts ou=hosts,dc=example,dc=com nss_base_services ou=services,dc=example,dc=com nss_base_networks ou=networks,dc=example,dc=com nss_base_protocols ou=protocols,dc=example,dc=com nss_base_rpc ou=rpc,dc=example,dc=com nss_base_ethers ou=ethers,dc=example,dc=com nss_base_netmasks ou=networks,dc=example,dc=com nss_base_netgroup ou=netgroup,dc=example,dc=com I filed a bug for this: https://bugzilla.novell.com/show_bug.cgi?id=498376 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] Screen blanking/locking and 11.1
by Clayton 28 Apr '09

28 Apr '09

This weekend I did a clean install of 11.1 and updated to KDE 4.2.2 Factory. Things are working great except for one thing... for some reason the screensaver starts after a fixed time of about 6 minutes. I've tinkered with the screensaver settings, and it's definitely the screensaver kicking in - if I set it to a specific screensaver type, that selected screensaver is what comes on in 6 minutes of inactivity. When the screensaver is on, the desktop is password locked. In Configure Desktop > Desktop > Screensaver, the screensaver is set to OFF. Setting it to ON, and changing the delay start time has no impact on the 6 minute delay. After 6 minutes, the screensaver starts regardless of the value in the "After" field. In Configure Desktop > Display > Power Control, Enable display power management is set to OFF. This seems to be working correctly as the screen is not placed into standby mode. In Configure Desktop > Advanced > Power Management, Lock screen is set to OFF, PowerDevil is set to OFF. After updating from KDE 4.1 to KDE 4.2.2 Factory I removed the plasmarc config files and forced a rebuild of the desktop config on the off chance this might fix the screenblanking thing. This did not help. There was a discussion on the list here a while back about an almost identical problem. I've read that thread, and tried the suggestions there - nothing suggested worked. The thread was mainly about getting screensavers working again in KDE3 instead of only having screen blanking. (solutions including linking KDE3 screensaver directories etc. t get screensavers working again) Does anyone have any ideas of what else I can try to convince 11.1 that I do not want my screen locked and I do not want screensavers to come on automatically after a 6 minute timeout? C. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 1