Re: Cygwin programs display output incorrectly when run under conemu
I had the same issue and got answer from Takashi Yano https://cygwin.com/ml/cygwin/2020-01/msg3.html My workareound is using version ConEmuPack.170807.7z. This works together with cygwin 3.1.2-1. Versions of Comemu greater 170807 won't. Same for cmder, if replacing conemu with version 170807. Hartmut Am 16.02.2020 um 13:22 schrieb Paul Moore: > This issue has also been reported to the ConEmu tracker as > https://github.com/Maximus5/ConEmu/issues/2059. > > If I run a cygwin command (for example ls, or for a simpler example, > "printf hello\nthere", although the latter needs care to get the > correct level of \n escaping :-)) newlines are displayed by the text > moving down a line, but *not* returning to the left hand margin. > > An example, running in Powershell as my shell: > >> E:\Utils\Cygwin64\bin\printf.exe hello\nthere > hello > there > > This behaviour is present with the latest version of cygwin1.dll, as > well as with the 20200212 snapshot. It is not present if I replace the > Cygwin dll with version 3.0.7-1. > > The problem does not appear with a standard cmd.exe terminal (standard > Windows console host) or the new Windows Terminal application. I > understand that ConEmu handles the console management differently > "behind the scenes" to present a GUI front end, but I don't know > enough about the internals to know how it does that. > > I can work around the issue by pinning to cygwin 3.0.7-1, but it's > obviously not ideal. I have been unable to find any details as to what > changed between cygwin 3.0.7-1 and the next version to help me track > down the issue any more specifically. > > There are some notes at https://conemu.github.io/en/CygwinMsys.html > that I've read, but to be honest I don't entirely understand. I did, > however, confirm that this issue doesn't occur in a standard `cmd` > window (and I added that information to the ConEmu issue report). > > Any information that would help to pin down the cause of this problem > would be very much appreciated. > > Paul > > -- > 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 > -- -- Dr.-Ing. Hartmut Bartels dr.hartmut.bart...@gmail.com dr.hartmut.bart...@t-online.de -- -- 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
output of ls / grep corrupted in cygwin 3.1.2-1 (x64) under conemu
Hello I am running win10 Pro 1903 x64. After update to cygwin 3.1.2-1 for the x64 Version the command "ls-l" misses the running in Conemu. There is a for every new line, but the new line starts in position where the line before finished, just 1 line deeper. This is true using cygwin in the conemu version 191012 and also cmder and cmdermini. If I start a plain MS console cmd.exe the output looks good. The error also occoures for grep command. Others I did not test. I tested also cygwin 3.1.2-1 under win7 Pro. Here everything works in cygwin 32 bit and 64 bit. Installing previous version cygwin 3.0.7-1 shows correct output for conemu, cmder and cmd.exe. Any help appreciated. Hartmut -- 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
building cygwin packages
Hello, I need to tweak and build some packages that depend on many others. Figuring out the recursive dependencies and build order is tedious. What is the easiest way to simply download and build *all* cygwin packages? I have disk space and cpu time. First, I would do 32 bit, then 64 bit. Tia, - Bartels -- 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: Launch a windows application from crontab
On 02/10/2014 07:13 AM, carl wrote: > I feared it :( What possibilities remain to me with a win7 system? The > background for my problem is a windows application that sometimes > crashes silently (it is still open but doesn't do what it should) and had to > be restarted. A big amount of Voodoo sounds interesting ;-) > but perhabs I should simply use windows scheduled tasks? I have many processes that I run in a service. Similar to your situation, some of these fail periodically, each for a different reason. My solution is to run them in a loop, using e.g. bash: while [ 1 ] ; do myprog ; done A separate monitor program, running in its own service, periodically checks each 'myprog' to see if it is still responsive. If it is not, the relevant process is simply killed, and the daemon reincarnates. For myself, I would not consider windows scheduled tasks. -- Bartels -- 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: chmod Not Working
On 12/30/2013 06:16 AM, Nithin Kurien wrote: When I type the following sequence of commands: cd ~; mkdir sample; chmod -R 0700 sample; stat -c "%a %u %g" sample; rm -rf sample; mkdir sample; chmod -R 0755 sample; stat -c "%a %u %g" sample the output is: 770 1001 513 775 1001 513 Why is chmod not working? OS: Windows 8 Pro 64-bit Cygwin Setup.exe Version: 2.831 (32-bit) That looks fine to me. What do you expect? -- - Bartels -- 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: Where can I look for an answer to a problem with Cygwin's Perl?
On 12/09/2013 06:54 PM, Jim Cant wrote: Thanks. Unfortunately, this dump() isn't what I need. I need to produce a dump of arbitrary program that has failed somewhere out of my control in the system. The system debugger as specified by the 'AeDebug' registry key needs to get called when the arbitrary programs fails. The system debugger (which I specify in the AeDebug key) get called and passed the PID of the failed program and creates the dump I need by invoking cdb. (cdb.exe is a command line version of WInDbg My problem is the system never invoked the system debugger in cases where the arbitrary program that fails was launched by Cygwin's version of perl. I have only two suggestions: 1) please don't top post on this list 2) run gdb and see what causes perl to (not) coredump But I cannot help wonder if the perl crash on activeperl is intentional. Have you tried other ports? Native linux does not dump. Why would it? Dumping any interpreter sounds like a pretty stupid plan. Your brother might at this very moment be logging a bug against activeperl for that particular behaviour. The only good approach I can think of is to re-define the backticks to explicitely dump. That is straightforward and possibly even portable. -- - Bartels -- 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: Where can I look for an answer to a problem with Cygwin's Perl?
On 12/09/2013 03:39 PM, Jim Cant wrote: I have a problem with Cygwin's Perl. If a process started by Perl (system(), `` (backticks) ) crashes, the system debugger never getsww called so I can't get a dump. Have you tried perl dump? http://perldoc.perl.org/functions/dump.html -- - Bartels -- 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: C:\cygwin\bin\cyggcc_s-1.dll: Loaded to different address
On 12/04/2013 05:53 PM, Corinna Vinschen wrote: On Dec 4 17:41, bartels wrote: On 12/04/2013 03:23 PM, Corinna Vinschen wrote: On Dec 4 14:53, bartels wrote: On 12/04/2013 02:11 PM, marco atzeri wrote: Il 12/4/2013 1:35 PM, bartels ha scritto: On 12/04/2013 01:23 PM, marco atzeri wrote: I am looking for the cause of the problem, so that I know how to prevent it. Or is the only answer to simply run rebaseall after installation? usually yes If that is the case, then why is it not part of the installation? currently, it is part of the installation /etc/postinstall/autorebase.bat.done $ cygcheck -f /etc/postinstall/autorebase.bat _autorebase-000444-1 Your attached cygcheck output claims something else. The rebase version should be updated to 4.4.1 as well. Don't think there is a mismatch: that output was Marco's, not mine. Unless I misunderstand . . . http://cygwin.com/ml/cygwin/2013-12/msg00085.html was your mail, so it's kind of hard to imagine that the attached cygcheck output was Marco's. Check the version numbers. It's _autorebase-000425-1 and rebase-4.4.0-1 in the cygcheck output. Okay, I see. It takes a cygwin expert to spot that one. No way I could tell that those two should match somehow. Ah, that is an interesting one: $ rebase -si rebase: failed to open rebase database "/etc/rebase.db.i386": No such file or directory ...this here means that rebase never created the database, which in turn could point to rebase crashing or not having sufficient privileges on /etc. Something like that. What happens if you stop all Cygwin processes, including any service you installed, then start dash, make sure you're in /bin, and then call `./rebaseall -p'. Any helpful output? How about this; sure looks like something is wrong: ./rebaseall -p gzip: stdin: unexpected end of file Yes, something is wrong. Looks like you removed the /etc/setup directory or the contents of that dir. The content is created and maintained by the setup installer and rebaseall needs the information. Don't play games with the files under /etc unless you want to break your installation. It was never the idea to break the installation :) But, evidently, I did botch my bundle, so to speak. Rebase is fine now; all I get is this harmless (?) message: /usr/lib/perl5/5.14/i686-cygwin-threads-64int/CORE/cygperl5_14_2.dll: skipped because nonexistent. Nonexistent is not the whole truth: it's just a dangling symlink. Sibling cygperl5_14.dll is fine Is that a bug or my doing? Thanks for your (plural, including Marco) most excellent help. -- - Bartels -- 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: C:\cygwin\bin\cyggcc_s-1.dll: Loaded to different address
On 12/04/2013 03:23 PM, Corinna Vinschen wrote: On Dec 4 14:53, bartels wrote: On 12/04/2013 02:11 PM, marco atzeri wrote: Il 12/4/2013 1:35 PM, bartels ha scritto: On 12/04/2013 01:23 PM, marco atzeri wrote: I am looking for the cause of the problem, so that I know how to prevent it. Or is the only answer to simply run rebaseall after installation? usually yes If that is the case, then why is it not part of the installation? currently, it is part of the installation /etc/postinstall/autorebase.bat.done $ cygcheck -f /etc/postinstall/autorebase.bat _autorebase-000444-1 Your attached cygcheck output claims something else. The rebase version should be updated to 4.4.1 as well. Don't think there is a mismatch: that output was Marco's, not mine. Unless I misunderstand . . . Ah, that is an interesting one: $ rebase -si rebase: failed to open rebase database "/etc/rebase.db.i386": No such file or directory ...this here means that rebase never created the database, which in turn could point to rebase crashing or not having sufficient privileges on /etc. Something like that. What happens if you stop all Cygwin processes, including any service you installed, then start dash, make sure you're in /bin, and then call `./rebaseall -p'. Any helpful output? How about this; sure looks like something is wrong: ./rebaseall -p gzip: stdin: unexpected end of file Thing is that I need to work with a fixed collection of packages. The rolling release offered by the installer is fine, but not exactly suited for a controlled release to an unsuspecting user. So, perhaps I made a mistake, or there is some unfortunate combination of versions. Anyway, I will upgrade my collection bundle and try again. Unless the error message immediately rings a bell for you . . . Thanks, -- Bartels -- 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: C:\cygwin\bin\cyggcc_s-1.dll: Loaded to different address
On 12/04/2013 01:23 PM, marco atzeri wrote: Thanks for your reply. Please note that I understand that the ad-hoc solution is to run rebaseall. Unfortunately, that is not always possible. why ? Tricky sometime, but possible always. Well, not exactly impossible, but these are production machines that belong to a customer. It is not practical to ask them to kill all processes and run rebaseall when this happens. Not to mention that there should be a tracker process reporting the issue in the first place. I am looking for the cause of the problem, so that I know how to prevent it. Or is the only answer to simply run rebaseall after installation? usually yes If that is the case, then why is it not part of the installation? I do not understand why it happens on the one Windows 7 machine and not the other. - - Bartels -- 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: C:\cygwin\bin\cyggcc_s-1.dll: Loaded to different address
On 12/04/2013 12:00 PM, bartels wrote: Hello People, Cygwin seems to have become very stable recently, which is a Good Thing for me. And then I saw this one: 0 [main] perl 10672 child_info_fork::abort: C:\cygwin\bin\cyggcc_s-1.dll: Loaded to different address: parent(0x32) != child(0x3A) What could be causing it? Please note that I understand that the ad-hoc solution is to run rebaseall. Unfortunately, that is not always possible. I am looking for the cause of the problem, so that I know how to prevent it. Or is the only answer to simply run rebaseall after installation? -- bartels -- 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
C:\cygwin\bin\cyggcc_s-1.dll: Loaded to different address
Hello People, Cygwin seems to have become very stable recently, which is a Good Thing for me. And then I saw this one: 0 [main] perl 10672 child_info_fork::abort: C:\cygwin\bin\cyggcc_s-1.dll: Loaded to different address: parent(0x32) != child(0x3A) What could be causing it? - - Bartels -- 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: Confused about several issues with setting up cron
On 09/24/2013 08:13 PM, KARR, DAVID wrote: 15 31593 [main] crontab 8612 fhandler_base::open_fs: 0 = fhandler_disk_file::open(\??\C:\Cygwin\var\cron\tabs\dk068x, 0x8000) 21 31614 [main] crontab 8612 open: -1 = open(tabs/dk068x, 0x8000), errno 2 There you go: the process has no write access to your crontab file (C:\Cygwin\var\cron\tabs\dk068x) Popular advice on this list is that you do not mix posix and windoze permissions. I have fallen into that trap myself. - bartels -- 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: Confused about several issues with setting up cron
On 09/24/2013 05:04 PM, KARR, DAVID wrote: -Original Message- From: KARR, DAVID Sent: Sunday, September 22, 2013 2:32 PM Subject: RE: Confused about several issues with setting up cron -Original Message- Sent: Sunday, September 22, 2013 12:46 PM Subject: Re: Confused about several issues with setting up cron On 09/22/2013 05:56 PM, bartels wrote: On 09/22/2013 03:00 AM, KARR, DAVID wrote: CYGWIN_NT-6.1 1.7.25(0.270/5/3) 2013-08-31 20:39 i686 Cygwin I want to set up a cron job, so I have to get cron configured. I'm trying to follow the instructions I can find, but I'm seeing several issues. I'm surprised that there's nothing in the user guide or the FAQ about setting up cron. I had to settle for the various questions about this on StackOverflow and others. >>> I want to set up a cron job, so I have to get cron configured. I'm trying >> to follow the instructions I can find, but I'm seeing several issues. >>> I'm surprised that there's nothing in the user guide or the FAQ about >> setting up cron. I had to settle for the various questions about this on >> StackOverflow and others. >> >> Must say your reporting of events is also lacking crucial elements >> If you re-install and give me more details, then I will try and answer your >> questions. > Ok. I assume you mean re-installing cron, not Cygwin. Yes, cron-config is what I meant. > > I followed the process described in the FAQ for removing a service. I then ran cron-config again. When I did this before, I selected to run cron as myself. I decided to make it run as the local system account this time (first running "passwd -R" and entering my password). It appeared to complete without errors or warnings. I did this in a "run as administrator" window. > > In a normal window, I then ran "crontab -e". I figured this would put me into "vi" with an empty buffer. It just returned to the prompt. You should see a vi session. Do you have vi installed? What is the value of EDITOR? Yes, I have vi installed. EDITOR was blank, but I tried setting it to "vi" and repeating the test, with no change. This could indicate a deeper problem, confusing not just cron. > I then ran "crontab crontab" (the "crontab" file in my current directory is the file with the one job I want to run), and then did "crontab -l". Nothing. Are you familiar with the crontab format? If not, try this: $ man 5 crontab Yes, I am familiar with it, but here's the crontab I'm trying to set, in any case: 0 * * * * monitorDataSource > > I then went back to the administrator window. I ran "cronevents". This didn't show anything more than the cron service being started. I then ran "cronbug". I'm attaching the gzipped copy of this. > You will have more luck running cron 'as yourself': it is straightforward. Running it as a privileged user is more complicated. Is there a specific reason why you want to run it as system? No, only because running it as myself didn't work. In any case, I tried stopping and removing the service and rerunning cron- config, running the service as myself. It didn't make any difference. No response from "crontab -e", and "crontab crontab" seemingly ignored. Nothing in "/var/log/cron.log", and nothing in "cronevents" except for the service stopping and starting. Any more ideas about this? I guess it is to do with privileges. cron works on my machines without fail: as system, and as privileged user If you look at the service $ cygrunsrv.exe -Q cron --verbose You can see that you can run cron from your own account like this: $ /usr/sbin/cron -n Anyway, the cron process needs read/write access to /var/cron/tabs/ No cron file there, means no cron jobs for you. The fact that you do not get an editor with 'crontab -e' is strange. I can only guess that EDITOR has a strange value, or crontab dies on privileges. Have you tried strace? $ strace -f crontab -e 2>&1 | tee strace.log You can probably see it dying. - bartels -- 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: Confused about several issues with setting up cron
On 09/23/2013 08:59 PM, bartels wrote: cron-config does not accept SYSTEM as a user Hmm, looking at the script, it would seem that cron-config is capable of configuring cron to run as system. - bartels -- 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: Confused about several issues with setting up cron
On 09/23/2013 08:08 PM, Andrey Repin wrote: Greetings, bartels! By the way: SYSTEM is not a user. Since when? Since Bill Gates stopped sleeping in his garage? :) $ passwd SYSTEM passwd: unknown user SYSTEM Without knowing too much about Windows internals, I have always considered SYSTEM to be a context, rather than a user. Your assumption is wrong. You are persuing a childish argument in semantics. I think we both know what the SYSTEM means. And windows loudly disagrees with you: $ net user SYSTEM The user name could not be found. Greatly simplifying, NT AUTHORITY\SYSTEM is a built-in access control group, under which whole system kernel works. You are saying it: SYSTEM is a UAC. Besides, your argument is off topic, as this thread is about setting up sshd. cron-config does not accept SYSTEM as a user Of course we both know that to be just a limitation of cron-config. - bartels -- 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: Confused about several issues with setting up cron
On 09/23/2013 04:44 PM, Andrey Repin wrote: Greetings, bartels! Greetings Andrey! By the way: SYSTEM is not a user. Since when? Since Bill Gates stopped sleeping in his garage? :) $ passwd SYSTEM passwd: unknown user SYSTEM Without knowing too much about Windows internals, I have always considered SYSTEM to be a context, rather than a user. Please give me your take, if you have more info. I am interested - bartels. -- 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: Confused about several issues with setting up cron
On 09/22/2013 05:56 PM, bartels wrote: On 09/22/2013 03:00 AM, KARR, DAVID wrote: CYGWIN_NT-6.1 1.7.25(0.270/5/3) 2013-08-31 20:39 i686 Cygwin I want to set up a cron job, so I have to get cron configured. I'm trying to follow the instructions I can find, but I'm seeing several issues. I'm surprised that there's nothing in the user guide or the FAQ about setting up cron. I had to settle for the various questions about this on StackOverflow and others. >>> I want to set up a cron job, so I have to get cron configured. I'm trying >> to follow the instructions I can find, but I'm seeing several issues. >>> I'm surprised that there's nothing in the user guide or the FAQ about >> setting up cron. I had to settle for the various questions about this on >> StackOverflow and others. >> >> Must say your reporting of events is also lacking crucial elements >> If you re-install and give me more details, then I will try and answer your >> questions. > Ok. I assume you mean re-installing cron, not Cygwin. Yes, cron-config is what I meant. > > I followed the process described in the FAQ for removing a service. I then ran cron-config again. When I did this before, I selected to run cron as myself. I decided to make it run as the local system account this time (first running "passwd -R" and entering my password). It appeared to complete without errors or warnings. I did this in a "run as administrator" window. > > In a normal window, I then ran "crontab -e". I figured this would put me into "vi" with an empty buffer. It just returned to the prompt. You should see a vi session. Do you have vi installed? What is the value of EDITOR? This could indicate a deeper problem, confusing not just cron. > I then ran "crontab crontab" (the "crontab" file in my current directory is the file with the one job I want to run), and then did "crontab -l". Nothing. Are you familiar with the crontab format? If not, try this: $ man 5 crontab > > I then went back to the administrator window. I ran "cronevents". This didn't show anything more than the cron service being started. I then ran "cronbug". I'm attaching the gzipped copy of this. > You will have more luck running cron 'as yourself': it is straightforward. Running it as a privileged user is more complicated. Is there a specific reason why you want to run it as system? - bartels -- 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: Confused about several issues with setting up cron
On 09/22/2013 05:56 PM, bartels wrote: On 09/22/2013 03:00 AM, KARR, DAVID wrote: CYGWIN_NT-6.1 1.7.25(0.270/5/3) 2013-08-31 20:39 i686 Cygwin I want to set up a cron job, so I have to get cron configured. I'm trying to follow the instructions I can find, but I'm seeing several issues. I'm surprised that there's nothing in the user guide or the FAQ about setting up cron. I had to settle for the various questions about this on StackOverflow and others. By the way: SYSTEM is not a user. - bartels -- 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: About ssh
On 09/22/2013 06:16 PM, Javier Vasquez wrote: On Sat, Sep 21, 2013 at 9:59 AM, Robert Klemme wrote: On Fri, Sep 20, 2013 at 11:36 PM, Javier Vasquez wrote: ... Did you actually start it? You can verify with "netstat -an" that something is listening on port 22 as a first quick check. Kind regards robert Yes, see: % netstat -an | 'grep' :22 TCP0.0.0.0:22 0.0.0.0:0 LISTENING TCP[::]:22[::]:0 LISTENING Though when attempting "ssh " there's a time out failure, :-( It looks like you have no routing to that port. What happens when you turn off the windoze firewall completely? To see if there is routing, I find it easier to use netcat Install netcat, disable sshd server, then run this: $ nc -lp 22 On your client, you run $ echo blah | nc 22 If you have routing, then your problem is in sshd - bartels -- 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: Confused about several issues with setting up cron
On 09/22/2013 03:00 AM, KARR, DAVID wrote: CYGWIN_NT-6.1 1.7.25(0.270/5/3) 2013-08-31 20:39 i686 Cygwin I want to set up a cron job, so I have to get cron configured. I'm trying to follow the instructions I can find, but I'm seeing several issues. I'm surprised that there's nothing in the user guide or the FAQ about setting up cron. I had to settle for the various questions about this on StackOverflow and others. Must say your reporting of events is also lacking crucial elements If you re-install and give me more details, then I will try and answer your questions. - bartels -- 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: cygpath -m behaviour change
On 09/18/2013 04:34 PM, David Griffiths wrote: Hi, the script is attempting to determine the directory in which it exists, so CURRENT_DIR is a bit misleading. This is so that it can access other files in the same package relative to it (quite a common technique I think). Might be helpful to have some examples: /home/dgriff> mkdir test /home/dgriff> cd test /home/dgriff/test> cygpath -m "file\.." ./ /home/dgriff/test> cygpath -m "file/.." cygpath: error converting "file/.." - No such file or directory /home/dgriff/test> cygpath -m "file\..\.." C:/cygwin/home/dgriff/ /home/dgriff/test> cygpath -m "file/../.." cygpath: error converting "file/../.." - No such file or directory /home/dgriff/test> touch file /home/dgriff/test> cygpath -m "file/../.." cygpath: error converting "file/../.." - No such file or directory /home/dgriff/test> cygpath -m "file\..\.." C:/cygwin/home/dgriff/ /home/dgriff/test> mkdir dir /home/dgriff/test> cygpath -m "dir/../.." C:/cygwin/home/dgriff/ Note that the backslash variant always works and all of these used to work under previous levels of cygwin. Conceptually, I have always considered relative paths to be relative to a directory. Your one liners are creating a path relative to a file. I think that approach is flawed and there is nothing wrong in the way cygpath works now. Yesterday's cygpath behaviour was probably not intentional. We have utilities like dirname and realpath available to help out. Just my thoughts . . . - Bartels -- 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: mt and tar fail on LTO-5 drives
On 08/21/2013 11:51 AM, Frank Fesevur wrote: 2013/8/20 Corinna Vinschen: This bug is present since 2004 and nobody noticed it. I guess that means there aren't many people out there actually partitioning their tape drives... FYI: we use cygwin tar on a daily base to backup one server to LTO2-tapes, but I have never partitioned a tape. Wasn't even aware it could be done. Partitioning was first introduced on LTO with LTO-5, accommodating LTFS. - Bartels -- 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: mt and tar fail on LTO-5 drives
On 08/20/2013 03:32 PM, Corinna Vinschen wrote: On Aug 20 13:57, bartels wrote: ) Thanks, I think we can close this one! Glad to read that. You could do me a favor, though. At the moment I have no tape drive on any Windows machine for testing. Can you please test the new `partseek' command in mt 2.4.0 which I announced a couple of minutes ago and see if it does what it advertises in `man mt'? Sure. How long does it take to propagate to the mirrors? All I see is 2.3.3.1 And would that be experimental, or current? - Bartels -- 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: mt and tar fail on LTO-5 drives
On 08/20/2013 11:05 AM, Corinna Vinschen wrote: On Aug 20 10:29, Corinna Vinschen wrote: On Aug 19 21:10, bartels wrote: On 08/19/2013 07:12 PM, Corinna Vinschen wrote: It would be interesting to see the OS error codes. If you run tar under strace, the trace output should contain a line like [...] write: Win32 error or [...] close: Win32 error The value of is what I'm curious about. Here is the error: 15692 21364024 [main] tar 5700 mtinfo_drive::error: write: Win32 error 1100 ERROR_END_OF_MEDIA. The OS really thinks the medium is at its end... ...or the *partition* is at its end. Something occured to me this morning. Are you using used tapes, rather than fresh ones? Are the tapes you're using partitioned, by any chance, maybe because LTFS partitions the tape in two partitions, one for the files and one for metadata? This would explain the low capacity you see in mt status output. If the tape is partitioned, the capacity returned by GetTapeParameters is not the size of the entire tape, but the size of the current partition(*). And partition 0 is probably the metadata partition. This also explains why you get a supposedly early ERROR_END_OF_MEDIA. The partition is just not bigger. Try this: $ mt -f /dev/nst0 setpartition 0 $ mt -f /dev/nst0 status 2 $ mt -f /dev/nst0 setpartition 1 $ mt -f /dev/nst0 status 2 Make that $ mt -f /dev/nst0 setpart 0 $ mt -f /dev/nst0 status 2 $ mt -f /dev/nst0 setpart 1 $ mt -f /dev/nst0 status 2 I wrote the setpart and mkpart commands before mt on Linux had them and naturally they are now using different strings. I'll have another look into mt to make it more compatible with mt on Linux. Well, Corinna, you really saved the day. I missed the partition stuff completely. $ mt -f /dev/nst0 status 2 drive type : 56 (STK 9840) tape capacity: 1419369472 KB remaining: 1324161024 KB current file : -1 active partition :1 current block: -1 cur logical block: 195351 General status bits on (109): ONLINE IM_REP_EN HW_ECC min block size :2 max block size : 524288 def block size : 131072 cur block size :0 density code : 58 (Ultrium LTO-5) Thanks, I think we can close this one! - Bartels -- 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: mt and tar fail on LTO-5 drives
On 08/19/2013 08:44 PM, Guy Harrison wrote: This *might* be useful.. http://www-01.ibm.com/support/docview.wss?uid=swg21393009 ..particularly.. http://www-01.ibm.com/software/sysmgmt/products/support/IBM_TSM_Supported_Devices_for_AIXHPSUNWIN.html Please bear in mind the page is for TSM (Tivoli Storage Manager) so even if you find your drive in there it still may mean you need a driver. It is often the case when an IBM driver is required that both the driver and drive firmware must match. I'm going to duck out now except to say one more thing. When I've had to install TSM on a windows machine & it's gone wrong it has always been the driver (or getting windows to use the right driver) at fault. Thanks Guy, but these troubles are only seen with tar / mt. Both drives work fine with LTFS. - Bartels -- 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: mt and tar fail on LTO-5 drives
On 08/19/2013 07:12 PM, Corinna Vinschen wrote:
It would be interesting to see the OS error codes. If you run tar under
strace, the trace output should contain a line like
[...] write: Win32 error
or
[...] close: Win32 error
The value of is what I'm curious about.
Here is the error:
15692 21364024 [main] tar 5700 mtinfo_drive::error: write: Win32 error 1100
I suppose there is nothing for cygwin to do, other
than adding some items to the 'density' list:
{0x44, "Ultrium LTO-3"},
mt already knows LTO-3 and 4.
Which version is that? I have mt V2.3.2 and do not see it in the code.
- Bartels
--
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: mt and tar fail on LTO-5 drives
On 08/19/2013 07:06 PM, Eliot Moss wrote: Not so much, yet. Presumably HP and IBM offer some kind of backup utility with the drive software, Sure: both drives work fine using LTFS. Plenty of bytes there. No problem at all. - Bartels. -- 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: mt and tar fail on LTO-5 drives
On 08/19/2013 07:12 PM, Corinna Vinschen wrote: To be really sure, you could add debug output to Cygwin's mtinfo_drive::get_mp function and rebuild the DLL: diff -u -p -r1.90 fhandler_tape.cc Gladly. I would like to close this one way or the other. Which package and which dll are you talking about? My knowledge of cygwin internals is nearly zero. - Bartels -- 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: mt and tar fail on LTO-5 drives
On 08/19/2013 06:31 PM, Eliot Moss wrote: First of all, it's not clear to me whether it is a Microsoft problem or a device driver problem. I would see what's known about the behavior of the devices and their drivers with the specific Windows version you have. Of course it could be that other tools don't need to ask those same questions, for some reason, so that they end up working fine .. Good thinking. Running W7 64 professional. It detects the HP drive and automatically installs some driver. This driver shows the same behaviour as the HP driver. And then there is the IBM driver. Not sure if W7 installs a default driver for that. Same story. What does that tell you? - Bartels -- 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: mt and tar fail on LTO-5 drives
On 08/19/2013 12:19 PM, Corinna Vinschen wrote:
On Aug 17 20:35, bartels wrote:
Hello People,
I have here two SAS connected LTO-5 drives: one IBM and one HP.
Both drives work work fine, but sadly mt does not.
The size reported by mt is a meager 35 GB, instead of the expected 1.5TB
I have tried both an older 32 bit and the 'current' 64 bit cygwin: same result.
Writing to tape works fine with tar, but the tape is quickly considered 'full'.
Is there any hope of fixing this? LTO-6 is already out there.
I don't know. Cygwin uses the Win32 tape API. The OS function
GetTapeParameters returns the capacity and the # of remaining bytes as 8
bytes LARGE_INTEGER value. The size of LT)-5 or LTO-6 should fit easily
into that.
I just checked that the value is stored within Cygwin as 8 byte long
long value, so no problem there. The mt tool prints the value as %lld
value, so it should print it correctly as 8 byte value. From what I can
see, the wrong value *seems* to be returned by the OS.
Also, the write(2) function does not check for the remaining bytes, so I
wonder why tar should fail prematurely, unless there's a problem with
the block number. The OS function GetTapePosition returns the current
block number as LARGE_INTEGER, but Cywin stores it in a 32 bit int. So
the block number overflows after 4 billion blocks. But even with a
small blocksize of 512 bytes this would only occur at about 2 TB of
data, long after the end of the tape. Despite that this is more of a
theoretical problem, the mtop struct to pass parameters to ioctl(fd,
MTIOCTOP, ...) only allows 4 byte count values anyway, even on Linux.
Another potential problem is if you try to use blocksizes > 64K. I don't
know if that's still a problem in newer Windows versions, but with older
versions including Windows XP, the OS didn't handle blocksizes > 64K
correctly and we got spurious error messages. Something about this
should be in the mailing list archives of old.
But the bottom line is, I have no way to test and debug that, since I
don't have access to an LTO-5 drive, nor do I have a Windows machine
with SAS controller. However, since Cygwin as well as the mt tool are
Open Source, maybe you can have a look and debug this issue?
Thanks for your time.
I did have a look.
The size reported to mt by the os seems to be the root cause: it is
38_247_858_176 bytes, instead of 1.5TB
My tar blocksize for the earlier test was 64 KB, within spec.
HP has a max blocksize 512 KB, which seems to work fine.
Still, it stops on an error after 36 GB (just as it does with -b 2048):
+ tar -f /dev/nst0 -c -b 524288 blah
tar: /dev/nst0: Cannot write: No space left on device
tar: Error is not recoverable: exiting now
mt reports matching capacity, remaining and block:
$ mt -f /dev/nst0 status 2
drive type : 56 (STK 9840)
tape capacity: 38247858176 B
tape capacity: 37351424 KB remaining : 2105344 KB
current file : -1 active partition :0
current block: -1 cur logical block:73373
General status bits on (10b):
ONLINE IM_REP_EN HW_ECC HW_COMP
min block size :2 max block size : 524288
def block size : 131072 cur block size :0
density code : 58 (Ultrium LTO-5)
The IBM drive shows similar numbers and behaviour, slightly
different error msg ('Cannot close' instead of 'Cannot write'):
+ tar -f /dev/nst1 -c -b 2048 blah
tar: /dev/nst1: Cannot close: No space left on device
tar: Exiting with failure status due to previous errors
I suppose there is nothing for cygwin to do, other
than adding some items to the 'density' list:
{0x44, "Ultrium LTO-3"},
{0x58, "Ultrium LTO-5"},
How do I best report this to Microsoft?
Any chance they fix it, you reckon?
- Bartels.
--
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
mt and tar fail on LTO-5 drives
Hello People, I have here two SAS connected LTO-5 drives: one IBM and one HP. Both drives work work fine, but sadly mt does not. The size reported by mt is a meager 35 GB, instead of the expected 1.5TB I have tried both an older 32 bit and the 'current' 64 bit cygwin: same result. Writing to tape works fine with tar, but the tape is quickly considered 'full'. Is there any hope of fixing this? LTO-6 is already out there. Thanks - Bartels # IBM ULT3580+HH5 SCSI $ mt -f /dev/nst0 status 3 drive type : 56 (STK 9840) tape capacity: 37108736 KB remaining: 37093376 KB current file :0 active partition :0 current block:0 cur logical block:0 General status bits on (410b8000): BOT ONLINE IM_REP_EN CLN HW_ECC HW_COMP min block size :1 max block size : 1048576 def block size :65536 cur block size :0 density code : 58 (unknown) Drive(r) Capabilities: -- fixed length blocks: yesvar length blocks : yes set block size : yesfixed partitioning : no select partitioning: no initiator partitioning : no get logical blockno: yeslogical block spacing : yes get absolute blockno : yesabsolute block spacing : yes logical block immediate: no absolute block immediate : no relative block spacing : yesbackward spacing : yes immediate rewind : yesfast EOM spacing : yes immediate spacing : no write marks immediate : yes filemark spacing : yeswrite filemarks: yes write long filemarks : no write short filemarks : no report setmarks: no setmark spacing: no write setmarks : no set report setmarks: no sequential filemarks : no sequential setmarks: no load and unload: yesun/load immediate : yes lock and unlock: yesun/lock immediate : no tape retension : no retension immediate: no erase on bop only : no erase immediately : yes long erase : yesshort erase: yes sw ejects media: no report write protection: yes report EOT warn size : no set EOT warn size : no data padding : no set data padding : no returns capacity : yesreturns remaining : yes hw error correction: no set hw error correction: no hw compression : yesset compression: yes set comp. on bop only : no report cleaning request: yes # HP Ultrium-5 $ mt -f /dev/nst0 status 3 drive type : 56 (STK 9840) tape capacity: 37351424 KB remaining: 37351424 KB current file :0 active partition :0 current block:0 cur logical block:0 General status bits on (410b): BOT ONLINE IM_REP_EN HW_ECC HW_COMP min block size :2 max block size :65536 def block size :65536 cur block size :0 density code : 58 (unknown) Drive(r) Capabilities: -- fixed length blocks: yesvar length blocks : yes set block size : yesfixed partitioning : yes select partitioning: yesinitiator partitioning : yes get logical blockno: yeslogical block spacing : yes get absolute blockno : yesabsolute block spacing : yes logical block immediate: yesabsolute block immediate : yes relative block spacing : yesbackward spacing : yes immediate rewind : yesfast EOM spacing : yes immediate spacing : no write marks immediate : yes filemark spacing : yeswrite filemarks: yes write long filemarks : no write short filemarks : no report setmarks: no setmark spacing: no write setmarks : no set report setmarks: no sequential filemarks : no sequential setmarks: no load and unload: yesun/load immediate : yes lock and unlock: yesun/lock immediate : no tape retension : no retension immediate: no erase on bop only : no erase immediately : yes long erase : yesshort erase: yes sw ejects media: yesreport write protection: yes report EOT
Re: squid command doesn't do anything
On 01/31/2013 05:52 PM, Larry Hall (Cygwin) wrote: On 1/31/2013 8:29 AM, leo wrote: I have confirmed that all these dlls already existed on my system. Still squid does do anything. OK, I installed squid and noticed that invoking /usr/sbin/squid from the command line doesn't seem to do anything for me either. It exits with a code of 1. But I don't know anything, really, about squid's operation. I certainly didn't make any changes to squid.conf and a quick look at the squid man page says that configuration is necessary for it to work. Have you consulted the squid home page to get info on how to configure squid? I had a look and no attempt is made to read the specified config file: $ strace -f /usr/sbin/squid.exe -N -f xxyx 2>&1 | grep xxyx 137 70537 [main] squid 16040 build_argv: argv[3] = 'xxyx' Normally, squid will print a message saying that xxyx cannot be opened. Evidently, it crashes before it gets to that point. - bartels -- 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: disk format question
On 01/08/2013 10:24 PM, Warren Young wrote: On 1/8/2013 08:38, bartels wrote: That may very well be true, but I have a friend called locate: I *had* a friend called "which", but he didn't find it. I have now unfriended him. ;) Very funny. Yeah, know thy friends, is true. Cygwin remains a mongrel, an alien, an exotic thing in almost hostile territory. In that case, you shouldn't be looking at /dev names anyway. They're assigned in order of device discovery, so the device that gets called /dev/sdb or whatever depends on what happened before your code ran. It turns out that it is even easier: the device was switched to read-only. I could not see that, because it is remote. And dd does not work on udf, but format.com has no such problems. In Disk Management, you can permanently assign a USB key a different drive letter than the default. Now when you put it in, it appears somewhere other than code blindly hard-coded with a /dev name expects. I know. We assign letters with diskpart. Does windows leave a trail when mounting? Oh, doubtless there's something buried in the NT device namespace, mentioned in the document I pointed you to. Maybe you could dump two copies of it and diff(1) them, and assume that the one line that appears in the output is the new device. No need for that, fortunately. Ugh. Well said. - bartels. -- 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: disk format question
On 01/08/2013 04:14 PM, Warren Young wrote: On 1/8/2013 06:59, bartels wrote: The windows format.com format.com hasn't existed since the DOS days. That includes the DOS-based versions of Windows, up through Windows ME. Under NT-derived versions of Windows, "format" is a built-in command in cmd.exe. That may very well be true, but I have a friend called locate: $ locate format.com /cygdrive/c/Windows/System32/format.com /cygdrive/c/Windows/SysWOW64/format.com /cygdrive/c/Windows/winsxs/amd64_microsoft-windows-format_31bf3856ad364e35_6.1.7600.16385_none_827dd459a3aa9980/format.com /cygdrive/c/Windows/winsxs/x86_microsoft-windows-format_31bf3856ad364e35_6.1.7600.16385_none_265f38d5eb4d284a/format.com And it even seems to work ;-) > claims the fs is write protected, but I hope dd can help out. It's worth a try, but if I had to take a blind bet on it, I'd say you're going to find that dd will give the same result. Cygwin is essentially a user-level process. If cmd.exe cannot do a thing, dd.exe probably can't, either. It is *possible* that unmounting the filesystem with the taskbar button will let you write to the raw device. But Windows being Windows, it's possible that will make it disappear from the system entirely, too. I cannot touch the gui. It may not be necessary, as format.com has a /x feature. The mtab is not very helpful: That's because Cygwin proper does not mount local filesystems. The Cygwin mount table just shows you Cygwin-specific mappings that it has added on top of what the underlying NT kernel has done. Okay, I see. My question is this: which device in /dev do I use? According to [this][1] it's probably /dev/sdb. But please do read through what I pointed you to first, and check its applicability carefully before attempting this. 'Probably' is not good enough when the goal is targeted destruction :) I need a solid automated procedure to locate my device. $ cat /proc/partitions major minor #blocks name 8 0 732574584 sda 8 1104391 sda1 8 2 245063542 sda2 816 976762584 sdb 817102400 sdb1 818 976657408 sdb2 832 4882808320 sdc 833131072 sdc1 834 4882675712 sdc2 848 3909092 sdd 849 3909091 sdd1 864 7566844 sde 865 7566016 sde1 880 31590400 sdf 881 31590400 sdf1 $ df -h Filesystem Size Used Avail Use% Mounted on C:/cygwin/bin 932G 62G 871G 7% /usr/bin C:/cygwin/lib 932G 62G 871G 7% /usr/lib C:/cygwin 932G 62G 871G 7% / C: 932G 62G 871G 7% /cygdrive/c D: 31G 31G 0 100% /cygdrive/d E: 102M 30M 73M 30% /cygdrive/e F: 234G 137G 98G 59% /cygdrive/f K: 3.8G 616M 3.2G 17% /cygdrive/k O: 4.6T 1.7T 3.0T 36% /cygdrive/o X: 3.1G 3.1G 0 100% /cygdrive/x Y: 4.6T 1.7T 3.0T 36% /cygdrive/y Z: 7.3G 46M 7.2G 1% /cygdrive/z [1] http://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-posixdevices Yeah, I had a look see on that page before and it is not all that helpful, for reasons you explained. Does windows leave a trail when mounting? Prospects are not good without it. Thanks for the help. - bartels -- 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
disk format question
Hello Forum, I frequently need to destroy a file system on removable media. The windows format.com claims the fs is write protected, but I hope dd can help out. The mtab is not very helpful: D: /cygdrive/d udf binary,posix=0,user,noumount,auto 1 1 My question is this: which device in /dev do I use? - bartels -- 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: Best practice for running pgsql under cygwin?
On 12/22/2012 05:18 PM, Ryan Johnson wrote: However, we're going to do classroom demos at times, including one where we have fun with different isolation levels; I'll need multiple students logged into the same database so they can mess with each others' interactive transactions. Postgres has a native Windows installer, does tcp very well and has excellent access control. It is not clear to me where cygwin comes in, or what it is you are trying to protect. - bartels -- 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: trouble accessing samba shares with spaces and/or parentheses
On 12/22/2012 03:30 PM, Andrey Repin wrote: More importantly, is it possible to mount a network share, using cygwin, so that it becomes visible/available in explorer? >> Again, no mounting is required. Open up Windows Explorer and type in the UNC (\\\) and there you are! > It would be that simple, if there were no credentials involved. It'll ask you for credentials, if that would be necessary. Or you can enter credentials beforehand, assuming you're using the same for one remote system. net use \\host\IPC$ * /user: Good idea, but I need this for an autonomous process. A service cannot open Windows Explorer. And windows does not allow credentials in the UNC, afaik. - bartels -- 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: trouble accessing samba shares with spaces and/or parentheses
On 12/22/2012 03:25 PM, Andrey Repin wrote: > No reason, really, other than the fact that Windoze forces us to access physical storage devices via the silly drive letters . What? Where did you get this impression? This is not true for 18 years at least. That is interesting. How do I use cygwin to copy files off any eSata disk without using a drive letter? Probably, I could let cygwin mount the fs somehow, using the volume name. But I do not know the volume name beforehand, because they are not my disks. - bartels -- 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: trouble accessing samba shares with spaces and/or parentheses
On 12/22/2012 12:27 AM, Andrew DeFaria wrote: Or you can just do $ # \'s doubled because bash swallows them and net use requires them. $ net use \\share Okay, I did not know the letter could be ommitted. More importantly, is it possible to mount a network share, using cygwin, so that it becomes visible/available in explorer? Again, no mounting is required. Open up Windows Explorer and type in the UNC (\\\) and there you are! It would be that simple, if there were no credentials involved. The scope of mounting seems to be limited to a process (tree). Every service must mount separately. That's not been my experience. Or have I missed something? Might have. What have you tried? Simple: 1) Let user xx mount a share with 'Map network drive', 2) use ssh to login as xx@machine and type 'net use': There are no entries in the list. It's the same for the services. I can give you the one-liners. Windoze seems to lack a system level mount, such as we see on *nix. It can be argued that there is no fundamental problem with this. But in practice I now need to manage credentials and connect/disconnect in several places (i.e. services). Some questions come to mind: * Is there a way for the service to find out which shares are mounted by the user (and which credentials)? * The (plaintext) credentials are known to the app. Can I use the windows vault in some way, via CredWrite() / CredRead() ? - bartels -- 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: trouble accessing samba shares with spaces and/or parentheses
On 12/21/2012 07:23 PM, Corinna Vinschen wrote: > So where can I find strace? In /bin. I don't suppose they come any easier :) Thanks. - bartels -- 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: trouble accessing samba shares with spaces and/or parentheses
On 12/21/2012 07:30 PM, Andrew DeFaria wrote: On 12/21/2012 10:11 AM, bartels wrote: So where can I find strace? Where did you look? $ type strace strace is /bin/strace strace is one of my favourite toys on linux. Somehow, I never located it on cygwin. Never just typed in the magic word :) The packaging is a little different here, and the searching not so easy. I expected a package. BTW: Why the insistence on mapping it to a drive letter? Everybody always does that and I don't understand why. Drive letters change. Some people hard code 'em in their scripts. This is a recipe for errors. Other people say sometimes that some Windows apps can't work with UNC paths. I don't know of any that have this problem anymore. Q:/ doesn't tell me where this directly is located... No reason, really, other than the fact that Windoze forces us to access physical storage devices via the silly drive letters . Not using drive letters would mean I have two different presentations: one for local storage and one for remote storage. When in Rome . . . And is there a way to mount a network share without a drive letter, using cygwin? More importantly, is it possible to mount a network share, using cygwin, so that it becomes visible/available in explorer? The scope of mounting seems to be limited to a process (tree). Every service must mount separately. Or have I missed something? - bartels -- 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: trouble accessing samba shares with spaces and/or parentheses
On 12/21/2012 06:19 PM, Corinna Vinschen wrote: On Dec 21 18:01, bartels wrote: On 12/21/2012 05:47 PM, Corinna Vinschen wrote: On Dec 21 17:20, bartels wrote: $ net use Q: "$(cygpath -w '//macau/X32 Backup-4(WD)')" "bartels" /user:"bartels" The command completed successfully. $ ls q:/ ls: cannot access q:/: Input/output error Please don't use DOS paths. Use POSIX paths like /cygdrive/q instead: http://cygwin.com/cygwin-ug-net/using.html#pathnames-win32 Naturally, I tried all flavours: $ ls /cygdrive/q/ ls: cannot access /cygdrive/q/: Input/output error Works fine for me using a Linux Samba share with space in it. Okay, that leaves the parentheses as the likely troublemaker. The thing is, people bring in disks, and I have no control over their volume / share names. Any more ideas? Where's Santa when you need him ;-) "Input/output error" is just an EIO. strace might show more useful information. EIO could be generated for a couple of reasons, for instance, the WIn32 errors ERROR_DISK_CORRUPT or ERROR_OPEN_FAILED are translated to the POSIX EIO. Another chance to get EIO is if something goes badly wrong trying to read a symlink. Or, that's always a chance, the OSX smb server doesn't support some system call used by Cygwin. It wouldn't be the first such FS. You must be Santa! I did not believe it, but I tried the same share names on a linux server: that works fine. Indeed it looks like a cygwin/mac problem. That still leaves me with a lot of unhappy users. So where can I find strace? - bartels -- 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: trouble accessing samba shares with spaces and/or parentheses
On 12/21/2012 05:47 PM, René Berber wrote: On 12/21/2012 10:20 AM, bartels wrote: [snip] $ net use Q: "$(cygpath -w '//macau/X32 Backup-4(WD)')" "bartels" /user:"bartels" The command completed successfully. $ ls q:/ ls: cannot access q:/: Input/output error Have you tried the correct way? ls /cygdrive/q Did actually. No difference. The bugger is mounted, that is the strange part: $ net use New connections will be remembered. Status Local RemoteNetwork --- OK Q:\\macau\X32 Backup-4(WD) Microsoft Windows Network or the alternative Network share way? ls "//macau/X32 Backup-4(WD)" Just did that. Same difference: $ ls "//macau/X32 Backup-4(WD)/" ls: cannot access //macau/X32 Backup-4(WD)/: Input/output error Is there a set of escape characters for spaces, parens and whatnot? - bartels -- 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: trouble accessing samba shares with spaces and/or parentheses
On 12/21/2012 05:47 PM, Corinna Vinschen wrote: On Dec 21 17:20, bartels wrote: $ net use Q: "$(cygpath -w '//macau/X32 Backup-4(WD)')" "bartels" /user:"bartels" The command completed successfully. $ ls q:/ ls: cannot access q:/: Input/output error Please don't use DOS paths. Use POSIX paths like /cygdrive/q instead: http://cygwin.com/cygwin-ug-net/using.html#pathnames-win32 Naturally, I tried all flavours: $ ls /cygdrive/q/ ls: cannot access /cygdrive/q/: Input/output error Works fine for me using a Linux Samba share with space in it. Okay, that leaves the parentheses as the likely troublemaker. The thing is, people bring in disks, and I have no control over their volume / share names. Any more ideas? Where's Santa when you need him ;-) - bartels -- 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
trouble accessing samba shares with spaces and/or parentheses
Hello Cygwin, I am experiencing problems with spaces and/or parentheses in samba share names. Changing the share name is not an option, because they are physical drives, connected to a mac. The following works fine from a dos box, and also from the gui with 'Map network drive', but fails miserably from the cygwin prompt. $ net use Q: "$(cygpath -w '//macau/X32 Backup-4(WD)')" "bartels" /user:"bartels" The command completed successfully. $ ls q:/ ls: cannot access q:/: Input/output error This is not a question of privileges or configuration: other shares with vanilla names work fine. The mac logs do not immediately reveal any clues. Considering that the dos box and the gui have access, I am inclined to blame cygwin. Any ideas? Thanks - bartels -- 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: Cygrunsrv and special Windows virtual accounts "NT SERVICE"
On 12/18/2012 05:57 AM, Andrey Repin wrote: what about '-w -' or a long-only option > like --null-pwd? I'd say, the latter. "-w -" looks like you are trying to read password from STDIN. I heartily concur for two reasons: 1) '-w -' really looks like like stdin/out 2) '-' is actually a valid password Let's go for --null-pwd bartels -- 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: Intermittent failures retrieving process exit codes
On 12/07/2012 08:54 PM, Tom Honermann wrote: I recently was able to produce a very small test case that reproduces this issue reliably on some machines: Your suspicion about a race condition may very well be correct: I can easily confirm the problem on both iron and virtual smp, but not on a single core virtual. I have two instances of your test case running for half hour on the same core, without any problem: 30k cycles without hickup. Apart from the immediate effect exposed by your script, I have reason to believe that the root cause also affects other running (smp) processes. bartels -- 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: [ATTN: Git maintainer] Is there a reason Git package depends on cvs/cvsps ?
On 12/06/2012 05:59 PM, Earnie Boyd wrote: > Is there a reason Git package depends on cvsps (and in result - cvs) package? > It doesn't looks like cvsps is required for daily Git operations. > Am I missing something? Git has M&Ps to allow you to clone a CVS repository using git commands. Seems like it is not a real dependency. On debian the package git suggests git-cvs Package git-cvs depends on cvsps, and suggests cvs bartels -- 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: SVN and executable permissions
Is there way to specify to svn on the command line or though a config file that these types of files should automatically have executable permissions? svn propset svn:executable "*" Bartels. -- 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: openssh: uid changes unexpectedly to cyg_server
On 05/10/2012 05:39 PM, Larry Hall (Cygwin) wrote: On 5/10/2012 8:51 AM, bartels wrote: Hi All, I have a situation where the uid changes to cyg_server unexpectedly when changing PATH: $ ( id; PATH=/cygdrive/c/devkit/msys/1.0.11/bin:/usr/bin:; id ) UID=1001(pleezy) GID=513(None) groepen=513(None),544(Administrators),545(Gebruikers),1000(HomeUsers) uid=500(cyg_server) gid=544(Administrators) groups=544(Administrators) The uid 500 is in itself strange, as it does not seem to belong to cyg_server The devkit directory looks normal: $ ls -l /cygdrive/c/devkit/msys/1.0.11/bin totaal 9100 -rwxr-xr-x 1 pleezy None 105472 25 mrt 2008 a2p.exe -rwxr-xr-x 1 pleezy None 162 26 aug 2008 awk -rwxr-xr-x 1 pleezy None 16896 26 aug 2008 basename.exe . . . It is causing tremendous problems in file access. Any ideas? Yes. You've changed the tool you're using when you changed your path. Try '( id; PATH=/cygdrive/c/devkit/msys/1.0.11/bin:/usr/bin:; /cygdrive/c/cygiwn/bin/id)'. You are right, of course. Now the question is how to use the devkit properly. Thanks, Bartels -- 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
openssh: uid changes unexpectedly to cyg_server
Hi All, I have a situation where the uid changes to cyg_server unexpectedly when changing PATH: $ ( id; PATH=/cygdrive/c/devkit/msys/1.0.11/bin:/usr/bin:; id ) UID=1001(pleezy) GID=513(None) groepen=513(None),544(Administrators),545(Gebruikers),1000(HomeUsers) uid=500(cyg_server) gid=544(Administrators) groups=544(Administrators) The uid 500 is in itself strange, as it does not seem to belong to cyg_server The devkit directory looks normal: $ ls -l /cygdrive/c/devkit/msys/1.0.11/bin totaal 9100 -rwxr-xr-x 1 pleezy None 105472 25 mrt 2008 a2p.exe -rwxr-xr-x 1 pleezy None 162 26 aug 2008 awk -rwxr-xr-x 1 pleezy None 16896 26 aug 2008 basename.exe . . . It is causing tremendous problems in file access. Any ideas? Thanks, Bartels Cygwin Configuration Diagnostics Current System Time: Thu May 10 11:27:49 2012 Windows 7 Ultimate Ver 6.1 Build 7600 Path: C:\cygwin\usr\local\bin C:\cygwin\bin C:\Windows\System32\system32 C:\Windows\System32 C:\Windows\System32\System32\Wbem C:\Windows\System32\System32\WindowsPowerShell\v1.0 C:\Ruby187\bin C:\Ruby187\lib C:\cygwin\bin Output from C:\cygwin\bin\id.exe UID: 1001(pleezy) GID: 513(None) =513(None) 544(Administrators) 545(Gebruikers) 1000(HomeUsers) SysDir: C:\Windows\system32 WinDir: C:\Windows USER = 'pleezy' PWD = '/home/pleezy' CYGWIN = 'nodosfilewarning xterm' HOME = '/home/pleezy' HOMEPATH = '\cygwin\home\pleezy' MANPATH = '/usr/local/man:/usr/share/man:/usr/man:' HOSTNAME = 'mos-v1-' TERM = 'xterm' SHELL = '/bin/bash' WINDIR = 'C:\Windows' SSH_CLIENT = '192.168.18.129 59353 22' OLDPWD = '/home/pleezy' USERDOMAIN = 'mos-v1-' SSH_TTY = '/dev/pty0' OS = 'Windows_NT' ALLUSERSPROFILE = 'C:\ProgramData' USERNAME = 'cyg_server' MAIL = '/var/spool/mail//pleezy' SYSTEMDRIVE = 'C:' LANG = 'nl_NL.UTF-8' USERPROFILE = 'C:\Users\pleezy' TZ = 'Europe/Amsterdam' PS1 = '\[\e]0;\w\a\]\n\[\e[32m\]\u@\h \[\e[33m\]\w\[\e[0m\]\n\$ ' LOGONSERVER = '\\MOS-V1-' SHLVL = '1' PATHEXT = '.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC' SEEN_BASHRC = '1' HOMEDRIVE = 'C:' COMSPEC = 'C:\Windows\system32\cmd.exe' TMP = '/tmp' LOGNAME = 'pleezy' SYSTEMROOT = 'C:\Windows' PRINTER = 'Microsoft XPS Document Writer' SSH_CONNECTION = '192.168.18.129 59353 192.168.18.38 22' INFOPATH = '/usr/local/info:/usr/share/info:/usr/info:' PROGRAMFILES = 'C:\Program Files' COMPUTERNAME = 'MOS-V1-' _ = '/usr/bin/cygcheck' HKEY_CURRENT_USER\Software\Cygwin HKEY_CURRENT_USER\Software\Cygwin\Program Options HKEY_CURRENT_USER\Software\Cygwin\setup HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\Installations (default) = '\??\C:\cygwin' HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\Program Options HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\setup (default) = 'C:\cygwin' obcaseinsensitive set to 1 Cygwin installations found in the registry: System: Key: c5e39b7a9d22bafb Path: C:\cygwin c: hd NTFS 65432Mb 22% CP CS UN PA FC d: hd NTFS 51196Mb 12% CP CS UN PA FC MARVIN Raid e: hd NTFS 16380Mb 42% CP CS UN PA FC CF-Card f: hd NTFS 25596Mb 14% CP CS UN PA FC Shuttle C:\cygwin/ system binary,auto C:\cygwin\bin/usr/bin system binary,auto C:\cygwin\lib/usr/lib system binary,auto cygdrive prefix /cygdrive userbinary,auto Found: C:\cygwin\bin\awk Found: C:\cygwin\bin\awk -> C:\cygwin\bin\gawk.exe Found: C:\cygwin\bin\bash.exe Found: C:\cygwin\bin\bash.exe Found: C:\cygwin\bin\cat.exe Found: C:\cygwin\bin\cat.exe Found: C:\cygwin\bin\cp.exe Found: C:\cygwin\bin\cp.exe Not Found: cpp (good!) Not Found: crontab Found: C:\cygwin\bin\find.exe Found: C:\Windows\System32\find.exe Warning: C:\cygwin\bin\find.exe hides C:\Windows\System32\find.exe Found: C:\cygwin\bin\find.exe Not Found: gcc Not Found: gdb Found: C:\cygwin\bin\grep.exe Found: C:\cygwin\bin\grep.exe Found: C:\cygwin\bin\kill.exe Found: C:\cygwin\bin\kill.exe Not Found: ld Found: C:\cygwin\bin\ls.exe Found: C:\cygwin\bin\ls.exe Found: C:\cygwin\bin\make.exe Found: C:\cygwin\bin\make.exe Found: C:\cygwin\bin\mv.exe Found: C:\cygwin\bin\mv.exe Not Found: patch Found: C:\cygwin\bin\perl.exe Found: C:\cygwin\bin\perl.exe Found: C:\cygwin\bin\rm.exe Found: C:\cygwin\bin\rm.exe Found: C:\cygwin\bin\sed.exe Found: C:\cygwin\bin\sed.exe Found: C:\cygwin\bin\ssh.exe Found: C:\cygwin\bin\ssh.exe Found: C:\cygwin\bin\sh.exe Found: C:\cygwin\bin\sh.exe Found: C:\cygwin\bin\tar.exe Found: C:\cygwin\bin\tar.exe Found: C:\cygwin\bin\test.exe Found: C:\c
