Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: jurgen DOT defurne AT philips DOT com To: cygwin AT cygwin DOT com Subject: Using cygwin from network drive [Was :Re: procps 010801-2 question] MIME-Version: 1.0 Message-ID: Date: Mon, 28 Apr 2003 10:02:36 +0200 Content-Type: text/plain; charset="us-ascii" Hello, all, I have solved my problem, and I think I know what was going on, but some of you can maybe confirm or deny what I am saying here. For migrating my Cygwin environment to the network, I used the following steps : - Create a backup of my mount moints - Unmount all mount points - Copy the complete cygwin tree from HD to network - Update DOS/Windows PATH to point to new cygwin/bin - Remount mount points on new paths - Start testing Some non-critical programs acted weird. Well, I forgot something to do. I have a startup script which starts up applications, but these applications are started from within Windows, using ftype and assoc settings. When I restarted them, they still used parts of the old cygwin tree, so I suppose at some level there was a conflict. Since most applications ran fine, I then changed the ftype setting, removed the old cygwin tree and then ran completely from the network drive. Under normal circumstances, all programs work fine. cygcheck -s generates an error when run inside a screen session (screen 3.9.13) or inside a terminal started from a screen session, but not when run from a normal dos box or from a shell (pdksh, bash) inside a DOS box. Just tested : it does not generate this error when run from strace, inside a box where I normally get this error. Added : one attachment Jurgen jurgen.defurne+FromInterNet AT philips DOT com Sent by: cygwin-owner AT cygwin DOT com 04/22/2003 11:40 AM To: "Elfyn McBratney" cygwin AT cygwin DOT com cc: (bcc: Jurgen Defurne/BRG/CE/PHILIPS) Subject: Re: procps 010801-2 question Classification: Elfyn, I do not have Administrator rights, so everything must be created as "Just Me". This is not a big problem, because Cygwin is used here only in a small group to automate tasks on Windows 2000 systems (corporate policy). Like I said before, now procps and strace work, and I do not know why... Jurgen "Elfyn McBratney" 04/22/2003 11:21 AM To: "cygwin" Jurgen Defurne/BRG/CE/PHILIPS AT EMEA1 cc: Subject: Re: procps 010801-2 question Classification: Unclassified Jurgen please keep replies on list. > Thanks. Here is the output of cygcheck. Btw. cygcheck > also does not run anymore from a shell prompt, but it > does run from a DOS command prompt. > > [...] When you installed Cygwin did you install for "All Users" or "Just Me"? If the prior, that may be the problem, as your mount table only contains user mounts. To go back to all user's re-run setup.exe and change the install for to "All users" and click through until the end (no need to update packages) and you'll see a message a long the lines of "Nothing to be done". Once setup.exe has exited reboot your system and see if that helps. BTW, I can't remember hearing success stories of doing a Cygwin install like this so it may not even work. P.S. cygcheck output attached for Cygwin Analysts. Elfyn [attachment "cygcheck.txt" deleted by Jurgen Defurne/BRG/CE/PHILIPS] -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/