From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 130928 invoked by alias); 26 Oct 2016 14:13:40 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 130917 invoked by uid 89); 26 Oct 2016 14:13:39 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=console, sk:filtere, filtered, corporate X-HELO: mail-oi0-f47.google.com Received: from mail-oi0-f47.google.com (HELO mail-oi0-f47.google.com) (209.85.218.47) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 26 Oct 2016 14:13:29 +0000 Received: by mail-oi0-f47.google.com with SMTP id y2so147861779oie.0 for ; Wed, 26 Oct 2016 07:13:29 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=p+lCeA+HwJc8WLeWfY1xWchZ8w60f3jLUD7ybSWnunY=; b=GDL7f7cAnzcBDdW4s8W2bopbrQdkKmLHwyKPTWIB+43gx0GQg4URAVIlirT9R/Ptlr K8r6sxk4lhL1hfd7zg5XPQJfBzY7r0RyLa+gKxia0APDq0gQpPhDUzJAj9F2clprLBPb Xij6GcGCdTLsGttkc/ze0AWir/dD53Dsi7lllVKUQ5vk0PgIAj5xN7ZlT0h1upZqEH0l 23CyFLVRQzpz4iKr9+ydEaQZk4ScjAZ0qwC/i2qcv5tFGyuzJnjwFxNZCLkTlvN4tJ/P DKIM+gxr9Eb3ni3rXP/pptjoGFDoUiZZkAmtMx2TtPPjKZKm1T19H2ZDC9SxU/noIpXR 0qrg== X-Gm-Message-State: ABUngvedwUyl7+9bh2LIUTHJry40CLEhglBOPvqumTNcCQhXECLINXeSLS0EvgWyP9CwPCpgAH+r03pAW3bNqw== X-Received: by 10.157.6.111 with SMTP id 102mr1572101otn.190.1477491207385; Wed, 26 Oct 2016 07:13:27 -0700 (PDT) MIME-Version: 1.0 Received: by 10.157.37.60 with HTTP; Wed, 26 Oct 2016 07:13:26 -0700 (PDT) In-Reply-To: References: From: Keith Christian Date: Wed, 26 Oct 2016 21:21:00 -0000 Message-ID: Subject: Re: issues with startxwin not loading x windows To: cygwin@cygwin.com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes X-SW-Source: 2016-10/txt/msg00271.txt.bz2 Michael, To limit information leakage, I do this for several pieces of software on my corporate PC. The sed script that you'll create is useful in many other "cleaning" operations as well. 1. Create a text file dump using cygcheck or by whatever method named "original_text_file" 2. Look for strings in "original_text_file" that you want filtered or changed. (I simply delete entire lines containing anything with a sensitive string, but you could obviously replace the string only.) 3. Add these strings to a sed file, e.g. "clean.sed" 4. To avoid matching short strings before long strings, run the command below to put the longest strings first, so that partial strings aren't replaced too early, causing misses later in the original_text_file: awk '{print length($0)";"$0}' clean.sed|sort -nr|awk -F\; '{print $2}'>clean.longest_strings_first.sed /sensitive_string_lowercase_002/d /sensitive_string_lowercase_001/d /sensitive_string_lowercase_000/d /SENSITIVE_STRING_UPPERCASE_000/d /SENSITIVE_STRING_MixedCase_000/d /username_lowercase_001/d /username_lowercase_000/d /SENSITIVE_STRING_001/d /^[0-9][0-9][0-9]*(/d /USERNAME_MixedCase/d /MACHINE_NAME_001/d /DOMAINNAME_001/d /DOMAINNAME_000/d /USERNAME_CAPS/d /LOGONSERVER/d /xyzcompany/d /XYZCOMPANY/d /CLIENTNAME/d /PuTTY/d /BLART/d /FOO/d 5. Run this command line to produce an output named "filtered_text_file" sed -f clean.longest_strings_first.sed original_text_file>filtered_text_file 6. I like to use the "vimdiff" command to show the changes from "original_text_file" to "filtered_text_file." vimdiff original_text_file filtered_text_file 7. Iterate over steps 2 - 6 editing "clean.sed" until it produces a clean.longest_strings_first.sed file that filters or modifies strings that you don't want in the output. On Fri, Aug 19, 2016 at 8:28 AM, Eliot Moss wrote: > Maybe I am way off base, but this seems similar to what will happen if a > .startxwinrc file's commands don't have something that waits. My > .startxwinrc > looks like this: > > #!/bin/bash > > xrdb -merge ${HOME}/.Xdefaults > xmodmap ${HOME}/.Xmodmap > > UC="${USER} console" > xterm +tb -geometry 110x62+4+0 -T "${USER}" -n "${USER}" -name "${USER}" > -bg rgbi:.0/.2/.2 -ls -iconic & > xterm +tb -geometry 110x62-10+0 -T "${UC}" -n "${UC}" -name "${UC}" > -bg rgbi:.5/.0/.1 -ls -iconic & > xemacs -iconic -geometry 110x61+0+0 -T xemacs & > wait > > > That is, it sets some defaults using xrdb and xmodmap and that opens two > xterms and one xemacs. > Note that those last three commands end in & ... they are this started in > background. The > 'wait' is very important here! Without it, the X startup process terminates > and then the > X server exits. > > Hope this helps, or at least does not add too much noise to the > conversation! > > Eliot Moss > > > -- > Problem reports: http://cygwin.com/problems.html > FAQ: http://cygwin.com/faq/ > Documentation: http://cygwin.com/docs.html > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple