Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Search results for query: *

  1. mubman

    Variable declarations

    Hi, A quite basic question I'm afraid. Somehow I had got it into my head that in C all variables must be declared at the start of a function block. Certainly this is convention and I would go so far as to say good practice. But from a quick test using a couple of different compilers it...
  2. mubman

    Checking if a file exists

    To expand slightly the file operators are generally unary boolean operators. i.e. they take a single argument (a scalar which evaluates to a filename or filehandle) and return true or false.
  3. mubman

    Checking if a file exists

    They are not command line switches! "perl -e" does something quite different. The code in my first post could be used as it is to form part of a perl program.
  4. mubman

    Checking if a file exists

    Yes, there are a number of file test operators - -w for a writeable file, -r for readable and so on. No doubt there's a complete list somewhere in the perl documentation.
  5. mubman

    Checking if a file exists

    Try something like: my $filename = "/usr/bin/perl"; -e $filename or warn "Perl is not installed correctly";
  6. mubman

    piping

    izivt Try this. open(AT,"at -f command 00:00 12/12/01 2>&1 |"); MB
  7. mubman

    piping

    izivt I am not a perl programmer in any way shape or form, but just a suggestion which may help. When used in the way you have the at command submits the at-job and writes scheduled time and at-job-id to standard error, not STDOUT. In order to capture standard error as well as STDOUT use |&...

Part and Inventory Search

Back
Top