On Fri, 2006-07-28 at 11:40 +0100, Chris Bradford wrote: > Paul Howarth wrote: > > On Thu, 2006-07-27 at 20:15 +0200, Alexander Dalloz wrote: > > > >> Chris Bradford schrieb: > >> > >> > >>> Unfortunately in my environment I still have a few windows (yes i > >>> know!) servers, and on one of them I am trying to make a script that > >>> will interpret a text file called 'disc.txt' that looks like this: > >>> > >>> jo tynan 15 Disc > >>> wdica KIML 1 > >>> Disc wdica > >>> sararyan 6 Disc rdpwd > >>> *There ARE spaces at the beginning of each line for some reason.* > >>> > >>> The file is generated every hour by the command: > >>> > >>> qwinsta /SERVER:servername | find "Disc" > disc.txt > >>> > >> I wouldn't have expected "find" in this command. Wouldn't that be "grep"? > >> > > > > I think the script is running on Windows, where "find" is a close as it > > gets to grep, and isn't the Unix-like "find" command. > > > > Paul. > > > > > > > Paul, > > You are right there, I was hoping to 'reverse engineer' a Unix like > command, but I'm not having much progress! > > -Chris Why try to reverse engineer it? Why not just use the source? -- Laurence Orchard *- This messages has been composed of completely recycled characters. -* *- Letters from previous messages have been broken down into their -* *- constituent bits and then reformed to make shiney, new characters. -* *- These new characters have then been pre-worn to fit in with your -* *- existing characters so they do not unduly stand out. -* *- This service is brought to you by Linux OpenSource Recycling, -* *- a GPL associate company. -*
