Re: scripting the "rec" function for a fixed time.

On Mon, Feb 24, 2003 at 07:01:03PM -0500, Peter Howell wrote: > I would like to be able to run the rec command unattended. Right now > when executed, it will record sound until I hit C-c. I would really > like to be able to right a script which will execute "rec ...", then > wait a specified peri

Re: scripting the "rec" function for a fixed time.

On Tuesday 25 February 2003 02:55, Ray Olszewski wrote: > At 07:01 PM 2/24/2003 -0500, Peter Howell wrote: > >I would like to be able to run the rec command unattended. Right now > >when executed, it will record sound until I hit C-c. I would really > >like to be able to right a script which will

Re: scripting the "rec" function for a fixed time.

At 07:01 PM 2/24/2003 -0500, Peter Howell wrote: I would like to be able to run the rec command unattended. Right now when executed, it will record sound until I hit C-c. I would really like to be able to right a script which will execute "rec ...", then wait a specified period of time, then pass

Re: su command broken

At 11:31 AM 2/25/2003 +0930, Adam Luchjenbroers wrote: using su to quickly login to root or to another user account fails, returning the error "invalid password" However, this password works fine to login from the login prompt. Where should I start looking to find the problem. With this little in

su command broken

using su to quickly login to root or to another user account fails, returning the error "invalid password" However, this password works fine to login from the login prompt. Where should I start looking to find the problem. -- "Windows isn't a virus, viruses do something" - Nowhere Man Please

scripting the "rec" function for a fixed time.

I would like to be able to run the rec command unattended. Right now when executed, it will record sound until I hit C-c. I would really like to be able to right a script which will execute "rec ...", then wait a specified period of time, then pass the C-c to it. Or is there a simpler way? Than

Question about TCP/IP

Hi Everyone, I have a program running over the TCP/IP network. Yet, sometimes it would deliver slow response time. Is there any good way to isolate/identify what is causing this? What would happen when the line is cut during transmission? IS there any particular timeout error need to be looked fo