Re: cron still not working - even after rerunning cron config
Greetings, Mike Brown! >> Sorry that I can't help you with your cron problem, but have you >> considered using the Windows Task Scheduler instead given the urgency of >> your situation? It can be used to kick off Cygwin processes just like >> any other. You'll need to wrap your existing tasks with a script in >> order to ensure that they receive the right environment, but that may be >> easier than debugging cron at this time. > I hate the Windblows task scheduler. nnCron, then? http://nncron.ru/ > Plus, while I am away I might have to remotely get in via ssh (which also > doesn't work) and change/add entries. That is best done using text editing. nnCron supports that, if memory not deceiving me. -- WBR, Andrey Repin (anrdae...@freemail.ru) 17.12.2011, <18:50> Sorry for my terrible english... -- 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
Re: Sorry "people" (NOT MY taxonomy!!), but igncr IS flawed
Hello Jeremy,
Many thanks for your reply. To be sure, I was quite incredulous myself bash
would have problems with empty lines, but that's what happens for me.
To be precise:
- I'm running Win7-64, Home Premium SP1
- I built Cygwin by running setup.exe with all the default options. The bash
is
Manu@Holland ~
$ bash --version
GNU bash, version 4.1.10(4)-release (i686-pc-cygwin)
- the script causing trouble comes in the GNU gdb distribution
gdb-7.3.1.tar.gz
- Notepad++ (sorry, a Win app) shows me that the problematic empty line
really contains just "[CR][LF]"
- needless to say, as I reported, ALL lines end that way (and ARE handled
correctly for most of them!), but that one is the first where "[CR][LF]" is
not preceded by anything in the line
- I'm uploading the script in case you'd find an opportunity to run it in
your Cygwin - in mine it stops with
Manu@Holland /cygdrive/d/Installs/gdb_7_3_1/gdb-7.3.1
$ ./configure
./configure: line 14: $'\r': command not found
./configure: line 29: syntax error near unexpected token `newline'
'/configure: line 29: ` ;;
Many thanks and Merry Christmas,
Emanuel
Jeremy Bopp-3 wrote:
>
> On 12/16/2011 11:13 PM, manu0507 wrote:
>>
>> Hi all,
>>
>> Notwithstanding the completely preposterous "reply" by Eric Blake (more
>> of
>> an idiotic acrimony, actually) to my previous post (see
>> http://old.nabble.com/Igncr-ineffective--tt32983438.html ), there does
>> seem
>> to be a problem in dealing with Win's CR/LF line endings in "unusual"
>> lines,
>> at least on Win7-64 (or, to be really precise, on my Win7-64).
>> The lines where CR/LFs appear not to be properly converted to LFs seem to
>> be
>> empty lines (except for the CR/LF, of course), as well as some other
>> "unusual" constructs (lines ending with ";;CR/LF" in particular).
>
> I don't have Cygwin available at the moment, so I can't try running
> scripts as you describe right now. However, the claim that a line
> consisting of only a CR/LF causing problems with the igncr option makes
> me pretty suspicious. "Empty" lines are pretty darn common in bash
> scripts, and I would expect to have seen many reports of problems with
> igncr reported here by now if that option didn't correctly handle those
> lines.
>
> Can you send a representative example script that elicits this problem
> for you? A simple test case would go a long way to addressing the
> issue. From the sound of things, no one else has reproduced your issue
> yet.
>
> Perhaps the lines that are giving you trouble are actually ended with
> CR/CR/LF. Have you examined the problematic scripts with a hex editor
> or simply "od -c" to verify the line endings?
>
>> To work around the problem, I'm writing an application that would convert
>> all CR/LF-ending text files into LF-ending ones... but it's not really
>> trivial, because telling binary files that should be left untouched from
>> text files that should be converted is difficult: even the very first
>> file
>> in GDB's sources ("configure") contains a '\a', i.e. a "not-text" byte.
>
> While it's not a complete solution by itself, I hope you're using the
> dos2unix or d2u programs to handle the conversion. You may also be able
> to make use of the file program from the file package to help identify
> files that are appropriate for conversion. Given that the igncr option
> is only useful for bash and maybe sh, scripts for those are probably the
> only ones you want to convert, and the file program should be able to
> identify them for you.
>
> -Jeremy
>
> --
> 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
>
>
>
http://old.nabble.com/file/p32994383/configure configure
--
View this message in context:
http://old.nabble.com/Sorry-%22people%22-%28NOT-MY-taxonomy%21%21%29%2C-but-igncr-IS-flawed-tp32989786p32994383.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
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
Re: Sorry "people" (NOT MY taxonomy!!), but igncr IS flawed
Dear Christopher, PLEASE read the three posts (the second one in particular) in the thread referenced below, and THEN decide who started the "rant". Thank you. Merry Christmas, Emanuel Christopher Faylor-8 wrote: > > On Sat, Dec 17, 2011 at 12:21:40AM -0600, Jeremy Bopp wrote: >>On 12/16/2011 11:13 PM, manu0507 wrote: >>>Notwithstanding the completely preposterous "reply" by Eric Blake (more >>>of an idiotic acrimony, actually) to my previous post (see >>>http://old.nabble.com/Igncr-ineffective--tt32983438.html ), there does >>>seem to be a problem in dealing with Win's CR/LF line endings in >>>"unusual" lines, at least on Win7-64 (or, to be really precise, on my >>>Win7-64). The lines where CR/LFs appear not to be properly converted >>>to LFs seem to be empty lines (except for the CR/LF, of course), as >>>well as some other "unusual" constructs (lines ending with ";;CR/LF" in >>>particular). >> >>I don't have Cygwin available at the moment, so I can't try running >>scripts as you describe right now. However, the claim that a line >>consisting of only a CR/LF causing problems with the igncr option makes >>me pretty suspicious. "Empty" lines are pretty darn common in bash >>scripts, and I would expect to have seen many reports of problems with >>igncr reported here by now if that option didn't correctly handle those >>lines. >>[...] > > Hats off to you, Jeremy, for your civility in responding to this rant. > > cgf > > -- > 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 > > > -- View this message in context: http://old.nabble.com/Sorry-%22people%22-%28NOT-MY-taxonomy%21%21%29%2C-but-igncr-IS-flawed-tp32989786p32994403.html Sent from the Cygwin list mailing list archive at Nabble.com. -- 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
Re: Sorry "people" (NOT MY taxonomy!!), but igncr IS flawed
On 17/12/2011 15:50, manu0507 wrote: > - the script causing trouble comes in the GNU gdb distribution > gdb-7.3.1.tar.gz Hah! I know what's happened: you used a windows program such as winzip or similar to unpack the archive, and it's gone and "helpfully" munged all the line endings for you. Use 'tar xvfz gdb-7.3.1.tar.gz' at the Cygwin shell command-line and you'll get a correctly unpacked version. (There definitely aren't CRLFs in the upstream release of the configure scripts.) Windows GUI-based archivers are well known for causing this problem. (Also, if you think that Eric's reply was "acrimonious", you're just having some sort of using-language-in-different-ways communication problem. I saw it earlier and it seemed perfectly polite and proper to me, I honestly can't see what about it would offend you.) cheers, DaveK -- 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
Re: cron log file empty
On Sat, Dec 17, 2011 at 09:04:38AM -0500, Pierre A. Humblet wrote: > cron logs to syslog, which by default uses the Windows log and which you > can read directly in Windows or filter with cronevents. Good to know for the future. > It's the first time I can recall where this is a problem, except for the > double entry in passwd. Do you use the crontab program to edit the crontab? Yes. I've never hand edited the output file created by crontab, always crontab -e. > It makes sure all ownerships/permissions are correct. Then it is doing a lousy job of it, otherwise it wouldn't bitch about ownership permissions. After I did a reboot, cron was no longer running as me, but as UID 0, so it started complainging about ownership again. As noted in a followup posting, I reverted back to 1.5 and all is well. MB -- e-mail: vid...@vidiot.com | vid...@vidiot.net/~\ The ASCII [I've been to Earth. I know where it is. ] \ / Ribbon Campaign [And I'm gonna take us there.Starbuck 3/25/07] X Against Visit - URL: http://vidiot.com/ | http://vidiot.net/ / \ HTML Email -- 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
Re: cron still not working - even after rerunning cron config
On Sat, Dec 17, 2011 at 06:52:16PM +0400, Andrey Repin wrote: > nnCron, then? > http://nncron.ru/ > nnCron supports that, if memory not deceiving me. As pointed out in a followup posting, I reverted back to version 1.5 and all is working again. MB -- e-mail: vid...@vidiot.com | vid...@vidiot.net/~\ The ASCII [I've been to Earth. I know where it is. ] \ / Ribbon Campaign [And I'm gonna take us there.Starbuck 3/25/07] X Against Visit - URL: http://vidiot.com/ | http://vidiot.net/ / \ HTML Email -- 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
Re: Sorry "people" (NOT MY taxonomy!!), but igncr IS flawed
On 12/17/11, Dave Korn wrote: > On 17/12/2011 15:50, manu0507 wrote: > >> - the script causing trouble comes in the GNU gdb distribution >> gdb-7.3.1.tar.gz > > Hah! I know what's happened: you used a windows program such as winzip or > similar to unpack the archive, and it's gone and "helpfully" munged all the > line endings for you. Use 'tar xvfz gdb-7.3.1.tar.gz' at the Cygwin shell > command-line and you'll get a correctly unpacked version. (There definitely > aren't CRLFs in the upstream release of the configure scripts.) Windows > GUI-based archivers are well known for causing this problem. 7-Zip (from sourceforge) also works for unpacking tar.gz files for use with Cygwin. > (Also, if you think that Eric's reply was "acrimonious", you're just having > some sort of using-language-in-different-ways communication problem. I saw > it earlier and it seemed perfectly polite and proper to me, I honestly can't > see what about it would offend you.) +1 Lee -- 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
Re: cron log file empty
On Sat, Dec 17, 2011 at 12:16:02PM -0500, Pierre A. Humblet wrote: > That's weird also because there is no uid 0 in the /etc/passwd you sent > earlier. You're right. I never even noticed that. Also explains why there wasn't a user name associated with the UID. D'Oh! > Could there be some confusion between 1.5 and 1.7? If so, then it is a problem with the setup when installing files onto a 1.5 previous install. There is zero information as to what to do/fix when installing 1.7 on the top of 1.5, even though one is instructed to read the docs for said things to look out for. There is nothing in the docs about going from 1.5 to 1.7. It would have been nice if there was a section that dealt only with this topic. Maybe I should have done to the 1.5 install what I did to the 1.7 install, when going back to 1.5, and that is wipe out all of the directories, other than my home. I wasn't able to remove the tabs directory, in that it complained that I didn't have the rights to do that (using windblows explorer to select and delete files/directories). MB -- e-mail: vid...@vidiot.com | vid...@vidiot.net/~\ The ASCII [I've been to Earth. I know where it is. ] \ / Ribbon Campaign [And I'm gonna take us there.Starbuck 3/25/07] X Against Visit - URL: http://vidiot.com/ | http://vidiot.net/ / \ HTML Email -- 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
Apparently solved! (Re: Sorry "people" (NOT MY taxonomy!!), but igncr IS flawed)
Hi Dave, Dave Korn-9 wrote: > > On 17/12/2011 15:50, manu0507 wrote: > >> - the script causing trouble comes in the GNU gdb distribution >> gdb-7.3.1.tar.gz > > Hah! I know what's happened: you used a windows program such as winzip > or > similar to unpack the archive, and it's gone and "helpfully" munged all > the > line endings for you. Use 'tar xvfz gdb-7.3.1.tar.gz' at the Cygwin shell > command-line and you'll get a correctly unpacked version. (There > definitely > aren't CRLFs in the upstream release of the configure scripts.) Windows > GUI-based archivers are well known for causing this problem. > My gosh, that's it! I Indeed extracted with WinZip... I WAS a bit suspicious, and looked in WinZip for an option like "Output text files in DOS format" or so that I could UNcheck, but having not found it, I thought WinZip would not be so intrusive as to modify the files that were compressed... Well, I never said Win was perfect, did I? ;-) That being said, it's still sort of beyond me why all [CR][LF]s would be converted ok... except the ones I reported. Dave Korn-9 wrote: > > (Also, if you think that Eric's reply was "acrimonious", you're just > having > some sort of using-language-in-different-ways communication problem. I > saw it > earlier and it seemed perfectly polite and proper to me, I honestly can't > see > what about it would offend you.) > > cheers, > DaveK > Ok, maybe Eric actually likes being called "people"... my fault then. Many thanks & Merry Christmas, Emanuel -- View this message in context: http://old.nabble.com/Sorry-%22people%22-%28NOT-MY-taxonomy%21%21%29%2C-but-igncr-IS-flawed-tp32989786p32995016.html Sent from the Cygwin list mailing list archive at Nabble.com. -- 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
Re: Sorry "people" (NOT MY taxonomy!!), but igncr IS flawed
On Sat, Dec 17, 2011 at 07:57:30AM -0800, manu0507 wrote: >PLEASE read the three posts (the second one in particular) in the thread >referenced below, and THEN decide who started the "rant". Thank you. I did read Eric's reply (which is the only one which would have any bearing). I know Eric. I know how he communicates in email and he is rarely, if ever, acrimonious. For instance, I have never seen him use words like "idiotic" or "preposterous". Your rant was uncalled for. cgf -- 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
Re: Apparently solved! (Re: Sorry "people" (NOT MY taxonomy!!), but igncr IS flawed)
On Sat, Dec 17, 2011 at 10:27:23AM -0800, manu0507 wrote: > That being said, it's still sort of beyond me why all [CR][LF]s would be > converted ok... except the ones I reported. It isn't a smart comversion, it is a blind substitute all conversion. MB -- e-mail: vid...@vidiot.com | vid...@vidiot.net/~\ The ASCII 6082066...@email.uscc.net\ / Ribbon Campaign Visit - URL: http://vidiot.com/ X Against http://vidiot.net/ / \ HTML Email -- 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
Re: Confusion with ACLs and Perl's file tests...maybe bug???
Reini Urban wrote: Thanks for the nice testcase. I'll try to take it upstream. But I'm not too confident that p5p will fix it, e.g. they refused to fix File::Copy::cp, keeping the perms as with /bin/cp for several years. I could recently fix the cygwin write check if you had admin rights though. --- I've noticed a distinct tendancy to want to keep broken, kludgy behavior, rather than fix it, because broken and kludgy is what makes perl special to them. OTOH, w/r/t/ the original problem, you have some calls that try to be 'posix compliant', and other calls that try to conform to NEW posix behaviors that aren't "officially" approved, but are adopted by most of the industry. But then you have conservative types who want to uphold "THE" posix standard (as if there is only 1). Last I counted, there were about 3 revisions that are not wholly compatible with each other, so having one set of tools want to stay stuck to one standard, while others try to move on, is a recipe for headaches, and those who decided to bawk at Larry's new Perl6 idea (for good reason, IM_personal_feeling), were also among the most conservative and least likely to change crowd -- meaning, fixing things, and moving to modern standards... That's a bit too scarey -- we don't know what might happen... so we better not do anything... Blech... Extremes are not usually good for humans... So ACLS are one of those 'new fangled things' that aren't on the officially approved list... so expecting those who want to adhere to the 15 year old standard based on practices that were in place at the time dating back 10 years prior, to actually move to the modern world, .. like expecting the Amish to learn Break Dancing... -- 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
