[NBLUG/talk] Odd cron problem

[Walter Hansen]

Hmmm. I should *******OHHHHH it's soo pretty outside right now, the fog is
surrounding the oak trees just perfectly ***** (sorry, ferret moment).
Anyway, I should ask my boss to pick those up for me. It's still very odd
though as the programs would complete running without once writing to the
file. Shouldn't they of at least written at the end if they were being
buffered? Oh, well, it's working now.

Crap, I have 10 more users/processes to add and I have to go in and one by
one create new passwords for them on two levels before 5:30pm. I'm going
to write a program to do this for me at sometime, but it's not enough of
an annoyance yet.

> On Mon, Dec 20, 2004 at 04:08:24PM -0800, Walter Hansen wrote:
>> That did it. Hmmm. A little bit of knowledge goes a short way, what did
>> I
>> do wrong?
>
> You were on the right track, earlier you wrote:
>
>> ... They should start getting information immediately and then slow
>> down to more every minute or so. I think perhaps it's somehow being
>> buffered, but I don't see how as all I've done is place the program
>> startup commands in the script file and made it executable.
>
> All Scott did was show you how to unbuffer Perls' output
>>> $|=1; select(STDERR); $|=1; select(STDOUT);
>
>> Any suggestions on where to look for stuff like this?
>
> Go with your suspicions and google for "perl buffered output"
>
> That brought up this link: (which probably legally shouldn't be on the
> web, but...)
> http://www.unix.org.ua/orelly/perl/cookbook/ch07_13.htm
>
> BTW, I *highly* recommend buying a copy of _The Perl Cookbook_.
>
> Also, _Programming Perl_ has some great pnemonics for remember Perl's
> weird shorthand special variables:
> $! "When you want your pipes to be piping hot."
>
> If I could, I'd buy both of those books in leather bound editions.
>
> -troy
>
>
> _______________________________________________
> talk mailing list
> talk at nblug.org
> http://nblug.org/cgi-bin/mailman/listinfo/talk
>
>