Re: ps -ef difference linux/cygwin (arguments)
I'll point out that there is also a significant difference between a direct response and gratuitous insults. William Sutton On Fri, 1 May 2009, Christopher Faylor wrote: On Fri, May 01, 2009 at 04:52:21PM +0200, jurri...@rivierenland.xs4all.nl wrote: From: Mark J. Reed Date: Wed, Apr 29, 2009 at 11:31:13AM -0400 This has come up before; an archive search might save some repetition. Yes, sorry about that. I can understand that the output of ps is used in scripts. I find it harder to understand that adding a new flag to ps would also break those scripts, You're assuming a fact not in evidence. but what I'd love most and suspect would keep this question from popping up and getting everybody excited now and again would be a small line in the ps man page. Well, the current "excitement" was apparently because I provided a one line direct response to a question rather than assuming that what was actually being asked for was a history lesson and a reminder that patches are thoughtfuly considered. Little did I know that there was an indignant person out there who was capable of speaking for lots of Cygwin users who languished in ignorance on this subject. Languishing aside, however, if someone is willing to provide a patch to provide a new option and new functionality, it will be given the same attention that we always give to patches. cgf -- 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/
Re: ps -ef difference linux/cygwin (arguments)
William Sutton On Wed, 29 Apr 2009, Mark J. Reed wrote: On Wed, Apr 29, 2009 at 11:13 AM, William Sutton Let's try this one again, and maybe we can be civil instead of condescending and insulting? Ahh. You must be new here. :) I've been using Cygwin for ~ 5 years and monitoring the list for ~ 3 years, so "new" might be relative. I can't say I've seen someone insulted quite so blatantly in that time :-/ This has come up before; an archive search might save some repetition. But if I understand the argument properly, it's a question of compatibility with scripts that expect the Cygwin ps to behave the way it does. Perhaps I should have searched the archive... The ps command has traditionally differed widely from implementation to implementation - the most glaring example being the BSD style options (ps auxgww) vs the SysV style (ps -elf). The modern Linux command attempts to integrate both styles, plus a third innovated by the GNU project, but the Cygwin ps command was already established as its own animal by the time that happened. (It also predates Cygwin's branding as specifically Linuxlike as opposed to generically Unixlike.) So there are configure scripts, etc. that check to see if the system is Cygwin and expect ps to behave in a certain way when it is. Making it act like Linux ps instead would break things, possibly lots of things, possibly unmaintained things. So instead, the procps(1) command is provided as an alternative for users who want a Linuxlike ps command on Cygwin. Thank you for a reasonable explanation :-) -- Mark J. Reed -- 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/
Re: ps -ef difference linux/cygwin (arguments)
Let's try this one again, and maybe we can be civil instead of condescending and insulting? There are certain expectations of UNIX and UNIX-alike environments, particularly core commands. When I move from Solaris to AIX to HP-UX to Linux to Cygwin, I expect commands to perform in fairly similar ways. I understand that in some cases, vendors like to be different (HP-UX and df, for example, or the entire GNU suite compared with AT&T or BSD UNIXes). In that respect, I expect ps to behave more or less the same across environments. I should not have to "know" in advance when I jump to a different platform excatly what the officially accepted replacement is to do a particular task. Sure, I can alias a command; I've done so many times. However the point you missed in your arrogant dismisal was not my particular memory, UNIX skills, etc., or those of an entire group of users. The point is that if Cygwin differs on a core command from standard UNIX procedure and has another command designed to accomplish the same functionality but not part of the generally known set of core UNIX tools, then maybe Cygwin should change to conform to the known and accepted standards of doing things. Regards, William Sutton On Wed, 29 Apr 2009, Christopher Faylor wrote: On Wed, Apr 29, 2009 at 10:52:27AM -0400, William Sutton wrote: That's a nice answer for a command that works, but, speaking for myself and a lot of other people who use cygwin for the UNIX-like utilities (like the OP), we shouldn't have to remember one-off command names to Maybe you and your memory-challenged ilk should invest in memory improvement drugs. Vitamin B12 is supposed to provide some benefits. Or, you could invest in a book on beginning UNIX commands so that you could figure out how to alias procps to ps. cgf -- 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/
Re: ps -ef difference linux/cygwin (arguments)
That's a nice answer for a command that works, but, speaking for myself and a lot of other people who use cygwin for the UNIX-like utilities (like the OP), we shouldn't have to remember one-off command names to get the same functionality we're used to in *NIX. Perhaps ps could be fixed to include the proper information instead if either having users languish in ignorance or be told to use some other command. William Sutton On Wed, 29 Apr 2009, Christopher Faylor wrote: On Wed, Apr 29, 2009 at 10:11:29AM +0200, jurriaan wrote: If I run execute some sh -c "sleep 180" & commands on cygwin (CYGWIN_NT-5.2 1.7.0(0.210/5/3) and then run ps -ef, I get a lot of /usr/bin/sh processes. If I run ps -ef on my linux (2.6.25.17), I get sh -c sleep 180 sh -c sleep 180 sh -c sleep 180 Is there any way to get the commandline arguments in the ps output on cygwin? I see theres /proc/XXX/cmdline that contains the correct information, but I'd love to be able to see it in ps as well. Use "procps" rather than "ps". cgf -- 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/
Re: cron does not do anything
Did you check that your cron job line is formatted correctly? If your line is literally of the form /usr/bin/touch /tmp/abcd then it definitely won't run because it is incorrectly written. William Sutton On Tue, 21 Apr 2009, Pierre A. Humblet wrote: - Original Message - From: "Ting Zhou" <> To: I'd like to report a bug with Vixie cron. I have cygwin installed with cron option. And I ran "cron-config" and set up everything. Cron-diagnose script didn't find any problem. Cron service was also started without problem. However, cron just wouldn't run the simple command I set up in the crontab "/usr/bin/touch /tmp/abcd". Hi, On your system you have syslog running, instead of using the Windows event log. That's fine, except that your syslog configuration now controls how the cron log messages are handled. The current "cronbug" script is not smart enough to figure that out and does not provide enough info to help you (everything looks normal to me) Please send us in attachment the file containing the cron logs (if they are kept). If it's very long, use "fgrep -i cron" to isolate relevant lines. Alternatively, stop both syslog and cron, then restart cron only, run the cronbug script again and send us the output. Pierre -- 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/
Re: DOS programs under "screen"
I suppose you could always use the 'clear' command instead of cls. If you need cls specifically, you can alias it to clear. From the edit point of view, is this something you could accomplish with another command-line editor (say vim)? William Sutton On Wed, 8 Apr 2009, James Calfee wrote: We need to run a DOS program as a service. The program provides valuable information in the DOS window in an interactive ASCII color interface but does not provide any method to connect to this interface if started as a service. One solution is to run this program under screen. Unfortunately, this will not work until I can get these things resolved: * DOS "cls" command does not work under screen * DOS "edit" program does not work under screen Does anyone know how to get these things working under Cygwin's screen? Steps to produce: Open a DOS window (start, run, cmd) or open Cygwin Run something like this> c:\cygwin\bin\screen cmd Or just> screen cmd ... Dos text and a prompt should come up .. Type> cls The command is echoed back but the console does not clear. Running 'edit' does basically the same thing too. Instead of seeing edit's blue interface, the command is echoed and the console hangs. Pressing Ctrl+C will terminate screen's session. These test do not use ANSI.sys (see absence of this device in /cygdrive/c/CONFIG.SYS).. The 'edit' program works just fine without it. Maybe screen can manage without it too. Any help is appreciated. Thanks, jc Disclaimer: This message (including attachments) is confidential and may be privileged. If you have received it by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. RxStrategies, Inc. shall not be liable for the improper or incomplete transmission of the information contained in this communication or for any delay in its receipt or damage to your system. RxStrategies, Inc. does not guarantee that the integrity of this communication has been maintained nor that this communication is free from viruses, interceptions or interference. -- 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/
Re: Strings command
I assume that $ which strings returns nothing? As far as I can tell, it's default in my environment at /usr/bin/strings. William Sutton On Wed, 18 Feb 2009, Milko wrote: Hi I'am a new user Cygwin. I have a question for your, which pachages i must install for a strings command and how install it. Sorry for my english, but I'am a Italian user. Regards Milko -- 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/
Re: programming API to determine whether in 'Cygwin environment'
All the same, you should probably check to see that whatever variables you choose to key off of don't alter the way your program behaves in other alternate Windows shells. A co-worker of mine uses 4NT, which provides UNIX command and shell emulation in a native Windows format. I expect it has at least $SHELL and/or $TERM. FWIW... William Sutton On Fri, 11 Jul 2008, Corinna Vinschen wrote: On Jul 10 22:32, Yitzchak Scott-Thoennes wrote: On Thu, July 10, 2008 10:06 pm, Christopher Faylor wrote: On Thu, Jul 10, 2008 at 08:49:06PM -0700, Tony Last wrote: My console program is built for native Windows (thus does not reply on cygwin1.dll). So I'm looking for a boolean method which will allow a program to tell whether it was run from within a Cygwin shell. A PATH containing colons which weren't preceded by just a single alphabetic character would be a clue but it wouldn't be foolproof. A HOME environment variable with no colons and forward slashes would be another clue. I don't think there is a foolproof test, though. Both HOME and PATH are translated by the time the non-cygwin program sees them, though?? $TERM would be set. That's very unlikely when started from cmd. $SHELL would be a hint, too. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/
Re: Wish Setup would accept my Perl
Having done a bit of this myself, I'm interested into enquiring further into your difficulties. Except for win32-specific modules, perl code *should* *just work* for either cygwin perl of for ActiveState. Last I checked (and it's been about a year), you should be able to get the win32-specific modules for cygwin as well, so I'm not sure why you can't just invoke the script in your bash shell and have it run. William Sutton On Thu, 6 Dec 2007, Michael Kairys wrote: DePriest, Jason R. gmail.com> writes: I have ActiveState Perl installed and cygwin perl. ... I have no problems when I use each version in the appropriate environment. Simple scripts can be written that will run in both environments. ... Cygwin handles the pathing so I never have a problem with a cygwin bash prompt trying to call C:\Perl\bin\perl when I just use 'perl'. It checks /usr/bin/perl first. I see that quite a discussion has evolved since last I checked this thread. Thanks to all of you who shared your experience and advice... I'm convinced that using AS Perl with Cygwin as I do is potentially unstable and I should not continue to ignore the issue. However after reading and re- reading all the posts I do not see a clear solution that fits with my usage. I would like to expand on that a bit and ask you to take one more pass at it. I originally got into Perl when I worked at DEC and needed a language in which I could write build scripts for Unix, VMS, and NT. Perl certainly helped me out there. However today I work almost entirely on Windows, except when I occasionally telnet into a Solaris server. Today, my Perl programs fall roughly into three groups: (1) Personal-use automation-glue scripts which never leave my machine and are likely to be Windows-specific (Registry, Clipboard, OLE) (2) Perl/TK programs that I share with my co-workers, again Windows-specific (3) A small number of scripts that I run on Solaris (but may test on Windows). I use Cygwin on Windows out of preference for the Bash shell, the Unix utilities, and the filesystem semantics. To be perfectly honest I use very little of the rest of Cygwin's wonderfully rich environment. I would be okay with maintaining two Perl environments, even if I had to do both PPM and cpan module management. However I want to type "perl foo.pl" at the Bash prompt and have foo.pl Just Work, whether it is written for AS or is generic enough that it could run under either. I just don't see how to make this work. I suppose I could rewrite my Bash aliases so "foo" equals "/c/Perl/bin/perl foo.pl" (it now equals "perl -S foo.pl") but I don't have all my scripts aliased and I'm used to finding them via the path. I could try "porting" all of my scripts that I can from AS to Cygwin but I really don't know what's involved there. I no longer use AS's debugger or their Komodo product since I discovered I could use Eclipse; but my scripts use Windows path semantics everywhere (in groups 1 and 2 anyway) and I'm sure there are other things that would break. (And I rather like the AS documentation :) I would appreciate any further thought you care to give this question, and TIA. -- 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/
Re: strange behavior with perl v 5.8.8
Nope, not a Cygwin specific issue.
I get the same behavior at the same point on Gentoo perl 5.8.8 (x86
dual-Xeon), Debian Etch perl 5.8.8 (x86 P4), and SunOS 5.10 perl 5.8.4.
William Sutton
On Thu, 27 Sep 2007, Andrew Louie wrote:
Hello,
I've run into a strange adding problem with perl:
when incrementing by 0.1 i get a strange behavior where at some
arbitrary number, it will append 0.99 to the end of the
number.
test case:
my $start = 0;
my $interval = 0.1;
my $end = 10;
do{ print "start: $start\n"; $start += $interval;}until($start >= $end);
Results:
...
start: 4.5
start: 4.6
start: 4.7
start: 4.8
start: 4.9
start: 5
start: 5.1
start: 5.2
start: 5.3
start: 5.4
start: 5.5
start: 5.6
start: 5.7
start: 5.8
start: 5.9
start: 5.99
start: 6.09
start: 6.19
start: 6.29
start: 6.39
start: 6.49
start: 6.59
start: 6.69
start: 6.79
start: 6.89
why all of suddun i get 5.9?
Is this a perl problem?
im using cygwin version 1.5.24
perl -v:
This is perl, v5.8.8 built for cygwin-thread-multi-64int
(with 8 registered patches, see perl -V for more detail)
--
-Andrew Louie
--
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/
Re: How to scroll up beyond the text in the cygwin window?
does it help if you do make check >make.log 2>&1 then look at make.log? -- William Sutton On Mon, 30 Jul 2007, mcbenus wrote: > > Hi Cygwin users, > I have a very basic question: Sometimes when I am running something with > cygwin the output text is so long, that even if I scroll up I cannot see all > the text. Is there a way to change it so that i could scroll more "history" > back? Or alternatively, can I type something that will save the written > text? > This happens to me for example when I type: 'make check' after installing a > program. > Thanks for your help! > BK > -- 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/
Re: hacked package on server
I remember an extensive discussion about the purpose MD5 sums serve for the cygwin installer[1] some time ago. My understanding (synopsis) of the thread (before I gave up reading it in disgust somewhere around Christopher Faylor's suggestion that the subject be dropped :} ) was that md5sum is only used to indicate that a particular package had been completely downloaded (someone correct me if I misunderstood, please). If that is the case, then it seems to me to be a bit quick to declare a server or package compromised based on a mismatch of md5 sums. I do think that instead of simply aborting the install with a message that the server was compromised (was it? or is something else going on?), that a more useful option would be to allow the user to select a different mirror and continue the process. -- William Sutton [1] http://cygwin.com/ml/cygwin/2007-05/threads.html#00314 On Mon, 16 Jul 2007, Louis Kruger wrote: > > > > On Mon, Jul 16, 2007 at 10:30:52AM -0500, Louis Kruger wrote: > > > I also have a complaint: the dialog that notifies the user of the failed > > > MD5 is not well designed. The dialog asks "Do you want to skip the > > > package?" and has a yes and no button. I read it quickly and pressed no > > > before thinking about it, the package went ahead and tried to install. I > > > think there should be a little more effort to restrain the user from > > > performing a dangerous action such as installing a package with a wrong > > > MD5. > > > > Good point. The message should probably be > > > > Do you want to not skip the package (No/Yes)? > > > > cgf > > I realize you are joking, but the wording of the message is beside the > point. For an ordinary end-user, installing a file with a wrong MD5 is > the wrong (and dangerous) thing to do in just about any case I can think > of. Therefore it should not be equally easy to select either option. > > My opinion is that the setup program should abort immediately on > detecting a wrong MD5 with a message that the server may have been > compromised. If there is a special case where someone may actually want > this, it should be something non-obvious, like a -allow-wrong-md5 flag > to the setup program. > > thanks, > Louis > > -- > 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/
Re: is perl braindead?
No...depends on where you run that script from. If you run it anywhere
outside of /bozo, it doesn't have the full path, so -d fails. If you
change your test to
if ( -d "$ldir/$_" ) { print "This is directory: $_\n"; next; }
then it works.
--
William Sutton
On Sat, 23 Jun 2007, Wynfield Henman wrote:
> From what I read the following should work, but it doesn't.
> Can one of you familiar with cygwin's perl help me out.
>
> Why doesn't the test, -d, for directory work on the subdirectory?
> It should, in my considered opinion.
> Below is sufficient code to perform a simple test.
>
> Your help is appreciated.
>
> Regards,
> wynfield
>
> prepare for the test from the command line:
> $ mkdir /bozo
> $ mkdir /bozo/bozo_the_clown_dir
>
> Check this:
> find /bozo -type d -print
> /bozo
> /bozo/bozo_the_clown_dir
> -- ok we have a directory and it has a subdirectory
>
> Sample code:
> -- start of simple perl program
> #! /bin/perl
>
> my $ldir="/bozo";
>
> if ( ! opendir DH, $ldir)
> {
> print "Couldn't open as a dir: $ldir. \n";
> exit 0;
> }
>
> print "Processing directory: $ldir\n";
> while ( $_ = readdir(DH) ) # will be either a file or directory
> name
> {
> if ( $_ eq "." or $_ eq ".." ) { print "dir . or ..\n"; next; }
> if ( -d $_ ) { print "This is directory: $_\n"; next; }
> print "Escaped detection $_\n";
> }
>
> close (DH);
> end of sample code
>
> --
> 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/
Re: password authentication fails in cygwin openssh windows xp pro
Although if you do want the standard bash dotfiles (.bashrc, .bash_history, .bash_profile), just copy them from /etc/skel to your new user directory and set owner/group based on the new user owner/group. -- William Sutton On Thu, 24 May 2007, René Berber wrote: > Dan Miller wrote: > > > OkRene you are the woman! Thank you so much. > > Er ... actually René is a male name, Renee is the female equivalent (I know, > there is Rene Russo and others that have the wrong name, but what do they > know, > the name comes from France). > > > I was sort of blowing > > off the event log because it appeared that windows couldn't determine > > what the problem was...but at the very end it said user dan not allowed > > because shell /bin/bash is not executable. so I chmod 700 /bin/bash.exe > > and I'm in!! It worked It actually worked!! :-) Any idea why this was > > set up this way...doesn't seem to be a problem I've come across in other > > peoples efforts to get this going. > > No, I've never seen this, very strange. I have 750 for bash's permissions > (-rwxr-x---), your other user may have problems if both login at the same > time. > > > Anyway, so now I can ssh into the computer as user dan which has a > > local login etc. I want to add another user that has a user account on > > the computer but is not allowed to login interactively to windows. Can > > you tell me how to do that? > > The user needs a password... and he might not have a home directory (on first > login it is created by the shell). > > > I can't seem to su within cygwin to rerun > > ssh-user-config. How do I set up another user in cygwin and then switch > > to that user and run the ssh-user-config script? I made a folder in the > > home directory for the new user, but it doesn't have the standard bash > > files. Thanks again! > > The new user doesn't need to run ssh-user-config, that only creates the > default > ~/.ssh directory with some defaults, and the keys which are only necessary for > public key authentication. You can login as the second user as it is now, > just > make sure the home is the correct one, then he can run the script. > -- 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/
Re: password authentication fails in cygwin openssh windows xp pro
just jumping in but... try ssh -vvv localhost >file 2>&1 to redirect STDERR to STDOUT in hopes of catching the output William (who is now stepping back out of the discussion) --snip-- > Rene, > > Thanks for taking the time to respond. > > I can't figure out how to get the output of ssh -vvv localhost to a file. > I tried ssh -vvv localhost > file.txt and the file is created but empty. > > Dan > --snip-- -- 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/
Re: DualCores and Current Cygwin problems
I'm running Cygwin, Windows XP professiona 2002 SP2, and Norton AntiVirus (with the firewall turned off) without problems on an Intel Core2 Duo 2.13 GHz system. -- William Sutton On Thu, 10 May 2007, Brian Salter-Duke wrote: > On Wed, May 09, 2007 at 10:07:20AM -0400, Christopher Faylor wrote: > > On Wed, May 09, 2007 at 09:54:36PM +0800, Chee Kiang Goh wrote: > > >Looking forward nevertheless to a better co-existence solution with > > >WindowXP/DualCoreCPU. This feature had been the primary reason why I > > >stick to cygwin over the years :> > > > > FYI, there is no better coexistence solution contemplated. > > > > PTC, although, you have to wonder why we'd have to accommodate virus > > checkers or firewalls, which are supposed to be unobtrusive. > > It is indeed a bit of a worry. I have just installed Cygwin and Norton > securities on a new dual-core laptop. I have seen no problems so far. Is > there anything in particular I should look for? > > Brian. > > > cgf > > > > -- > > 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/
RE: Problem running Cygwin Apache2 as Windows XP service
> > - vhost in /srv > > - mounting cgi-bin off a Samba export from a Linux box > > Do you have CYGWIN=smbntsec? > I don't believe so: $ env |grep CYGWIN CYGWIN=server Would it be beneficial for me to do so? > > cygrunsrv -I apache -d "CYGWIN apache" -p /usr/sbin/apachectl2 -a "start" > > (user set as the local 'William Sutton' user) > > Maybe the -i flag would help it behave more like it does from the > commandline. -i on what? I don't see that option from either cygrunsrv --help or man apachectl2. > > > cheers, > DaveK > -- 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/
Problem running Cygwin Apache2 as Windows XP service
First off, hi to all of you :}
Now for the problem...
PROBLEM
I cannot get Apache 2 under Windows XP Professional to run as a service using
cygrunsrv. In the present configuration, when I attempt to run a simple
environment variables cgi script, the error log tells me:
| [Fri May 04 14:01:16 2007] [error] [client XXX.XXX.XXX.XXX] Symbolic link not
| allowed or link target not accessible: /srv/www/cgi-bin
I'm thinking that the presense of symlinked directories shouldn't matter since
the configuration works just fine when apachectl is manually run via an xterm.
I've tried this using the SYSTEM user, my user, real directories, etc., with
no luck. From the command line, it works like a champ. Run as a service, it
fails.
Any thoughts on what to do (details follow)?
CONFIGURATION
Software:
- Windows XP Professional version 2002, SP 2 (Intel core 2 duo)
- cygwin 1.5-24.2
- cygrunsrv 1.17-1
- apache2 2.2.3-1
Environment:
- Windows user is 'William Sutton'
- Cygwin user is 'william' (I changed the user and home directory in my
cygwin /etc/passwd file for my convenience)
- Cygwin/X (I'm a *NIX guy, but need Windows too)
Apache Configuration:
- Apache is installed and runs properly when started from xterm via
/usr/sbin/apachectl2 start (e.g., web pages load, cgi programs execute as
expected, etc.)
- vhost in /srv
- mounting cgi-bin off a Samba export from a Linux box
- htdocs is local
- m{/var/log/apache2/([a-z]+.log)*}i are set to william:users, 0755 or 0644
- Service comfigured via
cygrunsrv -I apache -d "CYGWIN apache" -p /usr/sbin/apachectl2 -a "start"
(user set as the local 'William Sutton' user)
And in case anyone wonders why I need this to be running on Cygwin, I have to
generate some Word docs from a cgi script and I already have Cygwin installed.
--
William Sutton
--
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/
