to review.. the problem (UNIX style lines converted to DOS):
--v-v--C-U-T---H-E-R-E-v-v--
bash-2.05b$ printf "\r\n\n"|perl -pe '1;'|od -a
000 cr nl cr nl
004
work around:
--v-v--C-U-T---H-E-R-E-v-
d -a
000 cr nl cr nl
004
What am I missing, it's still broke. PERLIO=raw works fine
though..
bash-2.05b$ printf "\r\n\n"|PERLIO=stdio perl -pe '1;'|od -a
000 cr nl nl
003
bash-2.05b$ printf "\r\n\n"|PERLIO=raw perl -pe '1;'
ow imp it is. Looks like a
bug though - any comments would be appreciated.
__
thanks/regards,
Tom Rodman
pls run for my address:
perl -e 'print unpack("u", "\.\=\$\!T\http://www.cygwin.com/ml/cygwin-patches/2003-q1/msg00291.html
Frame 542 (158 on wire, 158 captured)
ators" was the real owner.
What am I missing? Is there a fix for this, or do I have an
incorrect config setting? I have included more background info below.
--
thanks/regards,
Tom Rodman
perl -e 'print unpack("u", "\.\=\$\!T\http://cygwin.com/ml/#unsubscribe-simple
Bug
odified a USENET script that uses the perl Win32::Perms module
from David Roth; the script works fine but does not show the flag I need.
thanks/regards,
--
Tom Rodman
--
PS
The Usenix perl script that I modified was called perms.pl. You
can pry it out of:
http://www.unetu.net/jiao
.
Yesterday I used a procedure that had worked many times (weeks earlier).
--
thanks/regards,
Tom Rodman
perl -e 'print unpack("u", "\.\=\$\!T\http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygw
This is just FYI, no response needed.
(BTW - I did get the answer to my post to via the package maintainer. )
--
thanks,
Tom Rodman
#
# header for first failed msg, sent ~12:47 CST 12/4/03
# o e-mail sent to the below From
re on the "#!" construct.
You just need to rethink your workaround..
I'm sure others can correct some of what I just said, but I believe
is mostly right ;->
--
Tom Rodman
pls run for my address:
perl -e 'print unpack("u", "1\:6UP\,\$\!T\http://cygwin.c
On Fri 3/26/04 1:15 EST :
>>The "#!" construct must always refer to a binary, never to another
>>script (to avoid loops?). I ran into the same issue. The UNIX
>>standard is what I just said, but earlier (and current?) cygwin
>>versions (wrongly) sorta supported a script. In 1.3.20 it works about
Assume you have two hosts w/cygwin installed: one that sees script
foobar as a local file and one that is running this same foobar but
through a network drive.
Based on tests, if bash is running the script "foobar", w/foobar
on a remote drive; then while foobar is
running on this remote box, assu
quot; showed this.
I read the help as saying up to 255 separate env vars may be
defined.
--
thanks,
Tom Rodman
perl -e 'print unpack("u", "1\:6UP\,\$\!T\http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation:
On Sun 4/18/04 13:15 +0200 Corinna wrote:
>I've uploaded version 1.0-1 which allows arbitrarily sized environment
>variables. The number of variables is still limited to 255.
Thank-you Corinna!
--
Tom Rodman
pls run for my address:
perl -e 'print unpack("u&
ntended?
I would like to see someone smarter than me argue that:
"\r" at EOL should never being stripped out of a
cygwin binary pipe.
Why shouldn't binary pipes behave the same in Cygwin and UNIX?
respectfully/regards,
Tom Rodman
--v-v--C-U-T---H-E-R-E--
Interactively rbash seems to work fine:
bash-2.05b$ uname -a; ln -s /bin/bash /bin/rbash;rbash
CYGWIN_NT-4.0 ws011206 1.3.20(0.73/3/2) 2003-02-08 12:10 i686 unknown unknown Cygwin
rbash-2.05b$ cd /
rbash: cd: restricted
When I set the login shell to /bin/rbash and login through ssh
the sh
Interactively rbash seems to work fine:
bash-2.05b$ uname -a; ln -s /bin/bash /bin/rbash;rbash
CYGWIN_NT-4.0 ws011206 1.3.20(0.73/3/2) 2003-02-08 12:10 i686 unknown unknown Cygwin
rbash-2.05b$ cd /
rbash: cd: restricted
When I set the login shell to /bin/rbash in /etc/passwd
and login thr
Consider the path:
/tmp/xxx/yyy/zzz
Within rxvt I want to doubleclick on "xxx" with the
result that only "xxx" is highlighted. Unfortunately
the complete path highlights. Interestingly enough
it works with "\", ie:
\tmp\xxx\yyy\zzz
Is there a switch to fix
t; switch on a domain controller would simplify
the cron script I use to automatically rebuild /etc/passwd.
--
thank/regards,
Tom Rodman
pls run for my address:
perl -e 'print unpack("u", "1\:6UP\,\$\!T\http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/
o finish
it for a few days; at that time I will followup later with a post that
follows the problem reporting guidelines.
--
thanks,
Tom Rodman
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation:
15.192:2682 ESTABLISHED
TCP10.125.15.180:1098 10.125.15.180:5413 ESTABLISHED
TCP10.125.15.180:1104 10.125.15.180:5413 ESTABLISHED
TCP10.125.15.180:1106 10.125.15.180:1339 ESTABLISHED
TCP10.125.15.180:1106 10.125.15.180:13
for eof, so output is flushed?
puts "\n\nexpect script exiting normally\n";
~ $ /tmp/fee
spawn ssh localhost -l staffuser1
parent: waiting for sync byte
Killed
~ $ # after a long wait, I manually killed "expect" from another bash session
--
Tom Rodman
--
Cygwin Configurati
Related ssh/expect script post by Corinna:
http://sourceware.org/ml/cygwin/2003-10/msg00801.html
FYI:
The Dec 16 cygwin1.dll snapshot test case "hung" again in the same way,
after I ran a "rebaseall" - just tried this 10 min ago.
Is it recommended that one do a rebaseall each time the cy
My guess is that cgf is aware of this, and working on a fix..:
~ $ uname -a
CYGWIN_NT-5.0 OurServer108 1.5.19s(0.148/4/2) 20051220 00:11:57 i686 unknown
unknown Cygwin
~ $ ssh localhost date
[EMAIL PROTECTED]'s password:
~ $
I manually entered the correct password above, the output fr
On Wed 12/21/05 12:36 +0100 cygwin@cygwin.com wrote:
> On Dec 20 23:00, Christopher Faylor wrote:
> > On Tue, Dec 20, 2005 at 07:02:12PM -0600, [EMAIL PROTECTED] wrote:
> > >There seems to be a new (related?) issue w/this Dec 20 snapshot. I don't
> > >have time to log the test formally now; I hope
connections are open:
#0 client-session (t4 r0 i3/0 o3/0 fd -1/-1 cfd -1)
debug3: channel 0: close_fds r -1 w -1 e 6 c -1
debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.4 seconds
debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0
debug1: Exit status 0
~ $
Problem: 'ssh localhost date' asks for password, I type it, I'm
authenticated, but no output is seen from the date command
(original post has details)
Corrina, and cgf wrote WJFFM:
http://cygwin.com/ml/cygwin/2005-12/msg00801.html
So what is special about my setup? What ad
Thanks Igor for your help, pls see strace results below:
On Sat 12/24/05 23:45 EST cygwin@cygwin.com wrote:
> On Sat, 24 Dec 2005, Tom Rodman wrote:
>
> > Problem: 'ssh localhost date' asks for password, I type it, I'm
> > authenticated, but no out
On Mon 12/26/05 16:01 EST cygwin@cygwin.com wrote:
--snip
> Hmm, you didn't attach the strace output -- just the sshd debug output.
> The command above will put the strace output into /var/tmp/sshd_strace.
> Also, there's no need to post the working case strace.
>
> FWIW, the strace output is like
On Mon 12/26/05 16:01 EST Igor wrote
--snip
> > > As an adaptation of your own command:
> > --snip
> > > Try:
> > >
> > > cygrunsrv -I sshd_test -p /usr/bin/strace.exe -a '-o
> > > /var/tmp/sshd_strace /usr/sbin/sshd.exe -ddd' -e CYGWIN="$CYGWIN"
> >
> > I setup the sshd_test service as you indi
Solving this issue is important to us. We have a tool
that triggers a remote job via an ssh client. If this
general approach works:
ssh remotehostname "job arg1 arg2.."
I think our tool will work.
On Mon 12/26/05 16:31 CST Tom Rodman wrote:
--snip
> my mistake, I just re-ran the
<2 informal tests on my home PC, /etc/ssh_config is "OTTB">
no problem, using PubkeyAuthentication:
$ uname -a #login shell is bash, started by 'sshing in'
CYGWIN_NT-5.0 argon 1.5.19s(0.149/4/2) 20051227 16:45:51 i686 unknown unknown
Cygwin
$ ssh localhost date
Wed Dec 28 21:03:43 CST 20
ase.
--
thanks,
Tom Rodman
On Tue 12/20/05 22:01 +0100 cygwin@cygwin.com wrote:
> On Dec 19 11:00, Tom Rodman wrote:
> > Enclosed is an expect script (to ssh to the localhost with password
> > authentication) that "hangs" (search ahead for "parent: waiting for sync
>
8 12:44:04 2006
from 127.0.0.1\r\r\nWelcome to Engineering Systems tcm server ..\r\n> 12:44:45
Sun Jan 08 0j tty3 2728 ~\r\r\n> OurServer108 staffuser1 >"
send: sending "date; exit\r" to { 4 }
date; exit
Sun Jan 8 12:44:46 CST 2006
logout
Connection to local
Believe this is correct, will someonelse pls verify? If so, is this
intended, ie permanent? If so, I need to adjust a script or two.
I'm aware that it %windir% is usually lower case for windows, but I
think it was changed to uppercase in an ssh cygwin session in previous
releases.
--
thanks,
Tom
On Sun 1/8/06 at 13:13 CST I wrote:
--snip
> The test case at the console may not have worked for the last several cygwin
> releases.
--snip
It's working just fine at the console under the 1/8/06 snapshot :->
--
Thanks!
Tom Rodman
--
At the risk of wasting bandwidth, here are
On Wed 1/4/06 18:39 EST Igor Peshansky wrote:
> On Wed, 4 Jan 2006, Christopher Faylor wrote:
>
> > On Tue, Jan 03, 2006 at 11:07:01PM -0500, Larry Hall (Cygwin) wrote:
> > >My output seems similar to Igor's, though mine is longer :-( (and therefore
> > >also bzipped) but definitely against the 12
On Thu 1/26/06 17:57 GMT "Dave Korn" wrote:
--snip
> I made the terrible mistake of trying to use M$ migwiz.exe to
> recover my old cygwin installation from a dead machine's drive to a
> new one.
>
> I thought it might be just a simple archiver that would conveniently
> help move all my stuff
velopers can author web sites on this computer
Members
---
The command completed successfully.
end The new local groups added today
}
-- background --
This host is in a large Active Directory Domain, with tho
ver.
To make the problem go away, run:
net localgroup toss_soon /delete administrators
BTW, we're unable to remove administrators from the group in
our case, and I prefer not to have to add the user to the group -
the account is already in the local administrators group.
--
thanks,
Tom
pls se
On Wed 2/1/06 10:20 +0100 cygwin@cygwin.com wrote:
> On Jan 31 10:32, Tom Rodman wrote:
> > Also notable, was that whoami shown: "OurSrvr064\sshd_server", instead of
> > "staffuser2".
>
> That's normal for passwordless login.
Sorry, I should have
by 'whoami', I'm refering to the *cygwin* 'whoami'
In addition, to 'whoami' reporting OurSrvr064\sshd_server,
the account does not have full rights. For details, see:
http://cygwin.com/ml/cygwin/2006-01/msg01495.html
--
thanks,
Tom
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-
On Wed 2/1/06 15:26 +0100 Corinna wrote:
> On Feb 1 08:07, Tom Rodman wrote:
> > On Wed 2/1/06 10:20 +0100 Corinna wrote:
> > > On Jan 31 10:32, Tom Rodman wrote:
> > > > Also notable, was that whoami shown: "OurSrvr064\sshd_server", instead
> > &g
[Informal post. I'm not a developer. Is this a fair test, does it have any
value?]
We have a test box (Windows Server 2003 Enterprise Edition), w/10GB RAM (PAE
enabled).
Trying to stress the limits of cygwin 1.5.19 or the OS, I ran this test
from a bash session:
# preliminary step: load priva
dentity in the old
domain. The files and dirs have SIDs from the old domain only, but the
SID history feature is supposed to make this moot.
Can we expect sensible output from 'ls -l'?
We'll be testing fairly soon; will post results back to this thread.
--
thanks,
Tom Rodman
-
thanks Corinna
On Thu 3/2/06 16:27 +0100 Corinna wrote:
> On Mar 2 09:13, Tom Rodman wrote:
> > Has anyone experienced a domain migration where the filesystem was
> > left unchanged, and a "SID history" was injected into Active Directory
> > trustees? Under "
On Fri 3/3/06 9:47 +0100 Corinna wrote:
--snip
> > The SIDs on several hundred GB worth of files and dirs will almost all
> > be from the old domain. The old domain controller will be shutdown,
> > but there will be a SID history associated w/(almost) each domain user
> > account and group that was
ine.
We're rebooting the server tonight - it's been up just over 1 week.
Should I try a later snapshot?
--
thanks much,
Tom Rodman
1st for for error on Monday:
--v-v--C-U-T---H-E-R-E-v-v--
> 16:09:13 Mon Mar 27 2j tty0 6480 /adm/config/etc
>
I installed the 3/29 cygwin1.dll snapshot yesterday on a test windows 2000 box.
Many
(all?) of our cron jobs ran normally Sunday morning. Today, though, the output
of 'ls' or 'ls -l' from an interactive bash session was always nothing.
I've reverted back to the released cygwin1.dll, and ls is work
On Sun 4/2/06 16:43 EDT cygwin@cygwin.com wrote:
> On Sun, Apr 02, 2006 at 02:37:22PM -0500, Tom Rodman wrote:
> >I installed the 3/29 cygwin1.dll snapshot yesterday on a test windows
> >2000 box. Many (all?) of our cron jobs ran normally Sunday morning.
> >Today, though,
On Sun 4/2/06 15:59 CDT cygwin@cygwin.com wrote:
> On Sun 4/2/06 16:43 EDT cygwin@cygwin.com wrote:
> > On Sun, Apr 02, 2006 at 02:37:22PM -0500, Tom Rodman wrote:
> > >I installed the 3/29 cygwin1.dll snapshot yesterday on a test windows
> > >2000 box. Many (all?) of
On Mon 4/3/06 13:19 EDT cyg wrote:
> On Mon, Apr 03, 2006 at 10:52:01AM -0500, Tom Rodman wrote:
> >Then, I ran:
> >
> > C:\>c:\aut\cyg\bin\strace -o/tmp/strace.out /bin/bash
> > bash-3.00$ exec /bin/ls -l /etc/passwd
>
> The strace shows that /bin/ls is
The latest versions of gawk and sed appear to have changed how they
process DOS text STDIN. This change in behavior has broken some of
our scripts. Is this change in behavior by design? Can we revert back
to the old design?
Pls see test cases below.
--
thanks,
Tom Rodman
DOS text STDIN. This change in behavior has broken some of
> our scripts. Is this change in behavior by design? Can we revert back
> to the old design?
>
> Pls see test cases below.
>
> --
> thanks,
> Tom Rodman
>
> # --
On Thu 4/6/06 8:04 CDT cygwin@cygwin.com wrote:
> OK - I read Corinna's ANNOUNCEMENT on gawk-3.1.5-4. I'll try the BINMODE
> variable.
I read the info page on gawk and BINMODE, it does not seem to be working:
~ $ cygcheck -c gawk
Cygwin Package Information
Package Version
On Thu 4/6/06 10:10 EDT "Luis P Caamano" wrote:
> On 6 Apr 2006 03:44:22 -, [EMAIL PROTECTED]
> <[EMAIL PROTECTED]> wrote:
> >
>
> > fork problem
> > 120469 by: [EMAIL PROTECTED] (J. David Boyd)
>
> I started using cygserver and edited its config file to use 310 procs
> instead of 62.
On Thu 4/6/06 13:46 EDT cgf wrote:
--snip
> >I just read
> >
> > /usr/share/doc/cygwin-doc-1.4/html/cygwin-ug-net/using-cygserver.html
> >
> >for the first time.
> >
> >We mainly run fairly straight forward bash and perl scripts under
> >cygwin, both at the commandline and through cron; some sc
On Tue 4/11/06 11:19 +0200 cygwin@cygwin.com wrote:
> On Apr 6 08:35, Tom Rodman wrote:
> > On Thu 4/6/06 8:04 CDT cygwin@cygwin.com wrote:
> > > OK - I read Corinna's ANNOUNCEMENT on gawk-3.1.5-4. I'll try the BINMODE
> > > variable.
> >
> >
the terminology), being imperfect;
so that may have convinced me to not use "rm -rf DIRXXX".
So is "rm -rf ./foo/" safe to use? Is there any danger that
anything other than ./foo/ will be deleted?
Thanks for any help, I'm mainly just curious. :->
--
Tom Rodman
--
--
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/
iles and dirs are written out with ownership, and posix groups
mapped as one would hope - to the matching accounts and groups in
the new domain. Very nice!
--
thanks,
Tom Rodman
--
PS
A couple of days ago, after re-reading the tar info pages, I decided to
try the --same-owner switch , and was pleas
Below is a nonsense set of commands derived from a useful script
that was getting fork errors w/the 4/27 snapshot:
~ $ date;uname -a
Tue May 16 07:58:20 CDT 2006
CYGWIN_NT-5.0 OurServer108 1.5.20s(0.155/4/2) 20060427 13:16:59 i686 Cygwin
~ $ cd /tmp;echo -ne '#!/bin/bash -u\nfoo "$@"\n' >b
Thanks to all for trying the test.
On Tue 5/16/06 21:20 PDT "Bryan D. Thomas" wrote:
> >> If I revert to the April 3 snapshot it works fine. For the 4/27
> >> snapshot, it's repeatable
>
> > I see this under 20060309 as well.
>
> This is repeatable on my system with both 20060427 and 20060309 ve
I tried the test case below w/the 5/27 snapshot and got
what appear to be the same fork errors. So, I'm sticking
with the 4/3/2006 snapshot.
Is there any other info I can supply to help?
--
thanks
Tom
On Wed 5/17/06 23:03 CDT cygwin@cygwin.com wrote:
> Thanks to all for trying the test.
--snip
I tried the test case below w/the 5/27 snapshot and got
what appear to be the same fork errors. So, I'm sticking
with the 4/3/2006 snapshot.
Is there any other info I can supply to help?
--
thanks
Tom
On Wed 5/17/06 23:03 CDT cygwin@cygwin.com wrote:
> Thanks to all for trying the test.
--snip
On Mon 5/29/06 12:13 EDT cygwin@cygwin.com wrote:
--snip
> I've reduced the size of the windows command line which is sent to
> Cygwin processes still further and that fixes the problem on my game
> computer. That fact that this worked just fine on my normal test
> computer (and presumably on Cori
ains just fine. I'm not a domain administrator - what rights do I
need ask our corporate admins to give my account so "mkpasswd -l -d"
completes w/o error? (I *am* a local administrator.)
--
thanks/regards,
Tom Rodman
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe
More background:
The box is running windows 2003 server.
The user running "mkpasswd" is a domain user (ie not a local computer
account). This user is in the host's local administrators group.
Help would be greatly appreciated :->
--
thanks,
Tom
Cygwin Configuration Diagnostics
Current S
ory admin though..
On Wed 3/2/05 14:03 CST Tom Rodman wrote:
> When running
>
> mkpasswd -l -d
>
> I get the error:
>
> mkpasswd (249): [5] Access is denied.
>
> See below bash session:
>
> [EMAIL PROTECTED] ~
> $ date; uname -a
> Wed Mar 2 10
> $ CYGWIN=nontsec touch foo
Thanks Brian, that should do it.
On Wed 5/18/05 13??:34 PDT Brian wrote:
> [EMAIL PROTECTED] wrote:
>
> > I like and depend on NTSEC, but sometimes I want pure windows behavior.
> >
> > How can I create a new file from the bash prompt without umask being
> > honored
On Wed 5/18/05 16:18 CDT Tom Rodman wrote:
> > $ CYGWIN=nontsec touch foo
>
> Thanks Brian, that should do it.
Here's a function I plan to use:
wtouch()
{
local file=$1
CYGWIN=nontsec touch "$file"
setacl -on "$(cygpath -aw "$file")" -ot fi
on
in the mail archives; I did read /usr/share/doc/Cygwin/openssh.README.
There is also a long delay (15 sec or so) when logging in.
--
thanks,
Tom Rodman
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation:
Interactively rbash seems to work fine:
~ $ uname -a
CYGWIN_NT-5.0 c7mkes108 1.5.17(0.129/4/2) 2005-05-25 19:38 i686 unknown
unknown Cygwin
~ $ ls -l /bin/{bash,rbash}
-r-xr-xr-x+ 2 scmcron Users 512512 Oct 29 2004 /bin/bash*
-r-xr-xr-x+ 2 scmcron Users 512512 Oct 29 2004 /bin/rbash*
bashrc but this
file is not read by prior to running "somecommand" above.
As a workaround I'm thinking of writing small c program wrapper
shell that does a "setenv" to set the path prior to calling rbash.
Sorry for the terse problem description, I know I'm rushing a bit.
Larry:
Thanks for taking the time to reply, and thanks for the (~/.bash_login)
suggestion.
Below are two tests cases for "ssh localhost date". The Linux
test shows that ~/.bashrc is read. The Cygwin case shows none of
~/{.bash_profile,.bash_login,.profile,.bashrc} are read. Doesn't this
seem lik
starting new thread, trying for attention :->
old thread: http://sources.redhat.com/ml/cygwin/2005-06/msg00306.html
Larry:
THANKS for taking the time to reply, and thanks for the (~/.bash_login)
suggestion.
Below are two tests cases for "ssh localhost date". The Linux
test shows that ~/.bash
--
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/
Greetings:
Not expecting help; want to share a problem
I have seen repeatedly every week or so on 1 host (windows 2000 server w/latest
service packs and fixes), using 1.5.17.
I have not seen a pattern or a cause, but I seem to recall that
the shell that "goes south", often (always?) has several s
ANDOM
touch: cannot touch `//OurBox108/scm/toss.7620': Permission denied
~ $ touch //OurBox108/scm/toss.$RANDOM
touch: cannot touch `//OurBox108/scm/toss.29272': Permission denied
I would appreciate it if anyone can try the above two cases
and let me know of they work OK for you.
--
Tom Rod
Pierre:
I may not be able to get back to this until Thursday, but I
will post again, with more detail (working or not working).
--
thanks again,
Tom
see comments below:
On Tue 7/26/05 17:26 EDT "Pierre A. Humblet" wrote:
> I don't follow exactly what you did, but you must make sure (show us !
Pierre:
On Tue 7/26/05 17:26 EDT "Pierre A. Humblet" wrote:
> I don't follow exactly what you did, but you must make sure (show us !)
> that "id" when you are logged in at the console reports exactly the same
> groups
> as when you are logged in under ssh.
>
> If there are fewer groups under ss
sing problems in ssh sessions; Pierre A. Humblet supplied
me with a workaround: (http://cygwin.com/ml/cygwin/2005-07/msg01287.html).
How can we determine if user staffuser1 is or is not in group
ABC_NA-CTX-Notepad-A?
--
thanks,
Tom Rodman
console bash session:
--v-v-
t" wrote:
> Tom Rodman wrote:
>
> > The 'id' command indicates user staffuser1 is in group ABC_NA-CTX-Notepad-A.
> > I use this account 'staffuser1', and have no idea what group
> > ABC_NA-CTX-Notepad-A
> > is; I do not think user staffuser1
not waited more than ~2 min
Not sure if this is exposing a bug. Just an observation.
--
regards,
Tom Rodman
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:
Thanks Larry.
The hang happens completely outside of cygwin also. It hangs
if you type "tlist bash" from a cmd.exe prompt.
--
Tom
On Wed 8/3/05 14:10 EDT Cygwin List wrote:
> At 11:25 AM 8/3/2005, you wrote:
> >Under 1.5.18 and several earlier releases the w2k resource kit tool "tlist"
> >hangs
see comments below, thanks again for your help. This
issue is pretty minor to me, but I had thought it might
be interesting to the list.
On Wed 8/3/05 14:10 EDT Cygwin List wrote:
> At 11:25 AM 8/3/2005, you wrote:
> >Under 1.5.18 and several earlier releases the w2k resource kit tool "tlist"
>
A 'tlist 5664' launched from the cmd.exe shell finished after ~20 min.
--v-v--C-U-T---H-E-R-E-v-v--
Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.
C:\Documents and Settings\staffuser1>timethis tlist 5664
TimeThis : Com
Greetings:
Our expect script, starts an ssh session on the localhost (w/password
authentication; login shell is bash), then starts another script. The
benefit- network drives are writable. This wrapper script is used in our
crontabs.
Recently (since 1.5.18, possibly earlier), this script
has been
hyperthreading
issues have been solved early this year - is this true?
--
My next workaround for this has been to abandon the expect
script, and the cygwin ssh client, and use a "plink" based
script instead.
--
thanks much,
Tom
On Sat 8/13/05 15:37 CDT Tom Rodman wrote:
> Greetings:
&g
On Mon 9/19/05 21:21 EDT Poor Yorick wrote:
> mkpasswd -d > /etc/passwd
>
> seems to hang. I get no output and it never completes.
For us, "mkpasswd -d" dumps ~1500-2000 users and then
errs out. Our domain is hugh. My work around is to build /etc/passwd
with a script that repeatedly calls "
s".
--
thanks/regards,
Tom
On Tue 9/20/05 15:05 BST "Dave Korn" wrote:
> Original Message
> >From: Tom Rodman
> >Sent: 20 September 2005 14:51
>
> > On Mon 9/19/05 21:21 EDT Poor Yorick wrote:
> >
> >> mkpasswd -d > /etc/passwd
> &
This problem is gone w/recent snapshots (I'm using the 9/19 snapshot).
--
thanks,
Tom
On Sat 8/13/05 15:37 CDT Tom Rodman wrote:
> Greetings:
>
> Our expect script, starts an ssh session on the localhost (w/password
> authentication; login shell is bash), then starts an
All:
I'm using the 9/19 snapshot. The sleep in the below test script seems to
be required, otherwise the script could be simplified and still
cause errors.
The test script works (always?) without errors on 1.3.20.
Here are a couple of test runs:
~ $ /tmp/test
x: 1
x: 2
x: 3
x: 4
x:
On Wed 9/21/05 11:44 EDT (cgf) cygwin@cygwin.com wrote:
> On Wed, Sep 21, 2005 at 09:13:09AM -0500, Tom Rodman wrote:
> >All:
> >
> >I'm using the 9/19 snapshot. The sleep in the below test script seems to
> >be required, otherwise the script could be simplified and
a position to upgrade cygwin on 9 servers, 3 of which
will be purchased in the next couple of months. :->
--
thanks again,
Tom Rodman
--
See below for the snippets { enclosed in curly
braces }. This is an egrep of last ~200 days of cygwin archives for:
fork: No such file or directory
died
= "LOCAL" S-1-2-0
The reason I care is that is that several tools we call from cygwin, will
not run unless the session is in S-1-2-0.
I'm not sure if this is a cygwin version issue, or due to windows 2003.
Any thoughts/can others test this in an ssh session?:
$WINDIR/syste
Thanks for your help Matthew.
On Wed 8/16/06 14:44 CDT mwoehlke wrote:
> Tom Rodman wrote:
> > Hosts effected:
> >
> > several boxes running windows 2003 server w/cygwin (1.5.20s(0.155/4/2)
> > 20060403 13:33:45)
> >
> > Problem (or feature?):
> >
On Wed 8/16/06 23:11 +0200 cygwin@cygwin.com wrote:
> On Aug 16 15:49, Tom Rodman wrote:
> > On Wed 8/16/06 14:44 CDT mwoehlke wrote:
> > > Tom Rodman wrote:
> > > > Hosts effected:
> > > >
> > > > several boxes running windows 2003 server w
On Fri 8/18/06 8:58 +0200 cygwin@cygwin.com wrote:
> On Aug 17 18:49, Tom Rodman wrote:
> >
> > tried that.. no joy, take a look:
> > --v-v--C-U-T---H-E-R-E-v-v--
> > $ $WINDIR/system32/whoami /all #we're in an ssh sessio
On Fri 8/18/06 16:28 +0200 cygwin@cygwin.com wrote:
> On Aug 18 08:35, Tom Rodman wrote:
> > On Fri 8/18/06 8:58 +0200 cygwin@cygwin.com wrote:
> > > On Aug 17 18:49, Tom Rodman wrote:
> > > >
> > > > tried that.. no joy, take a look:
>
On Wed 8/23/06 9:43 +0200 cygwin@cygwin.com wrote:
> On Aug 21 11:13, Tom Rodman wrote:
> > On Fri 8/18/06 16:28 +0200 cygwin@cygwin.com wrote:
> > > The trick using /etc/group only works for password-LESS authentication,
> > > sorry for not mentioning it, but usually
Greetings:
Admittedly just barely worth posting.. Over the years I've seen a
/bin/bash file, with 000 (-) perms. This file is empty, has no
extension, and bash.exe is not touched. How the zero byte "/bin/bash"
get's created is a mystery. It subsequently blocks you from 'sshing'
in. It was
1 - 100 of 148 matches
Mail list logo