Re: [SLE] rsync log

From: Jerry Feldman (gaf_at_blu.org)
Date: 12/01/03

  • Next message: Sean Rima: "[SLE] Re: SuSE 9.0 NTFS Read/Write"
    Date: Mon, 1 Dec 2003 15:08:59 -0500
    To: suse-linux-e@suse.com
    
    

    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA1

    On Mon, 01 Dec 2003 11:13:10 -0800
    Tom Nielsen <tom@neuro-logic.com> wrote:

    > First, kcron is for low-watt bulbs like me that aren't really sure how
    > to setup a cron task manually. If you type kcron you should get the
    > window pop up...if it's installed.
    >
    > Second, I didn't, and still don't, understand what you wanted me to do
    > with the > <... thing. Where do you want me to stick it? I mean should
    > I put it in the bash script I made (see below)?
    >
    > #!/bin/sh
    > rsync -auvzr --delete /home/tom/Documents/ /mnt/root2/
    >
    > What does stdout mean?
    Every process in Unix and Linux has 1 standard input from the terminal
    (stdin), 1 standard output to the terminal (stdout) and 1 standard error
    output (stderr).

    What this means is the non-error output from a command like rsync prints
    on the terminal, and you can redirect it using the right angle bracket
    (eg. >). The double right angle bracket means append.

    So:
    rsync -auvzr --delete /home/tom/Documents/ /mnt/root2/ > mylog
    Will direct the output of rsync to the file, mylog, in the current
    working directory.

    As I had mentioned earlier, the standard output of a cron job is emailed
    to the email address of the owner of the process, which would be tom if
    that is the user name you created your cron spec.

    So, if you do nothing, the output of your rsync command will be emailed
    to your user id. if you want that to go to another email address, set
    the mailto variable (using kcron). Select variables, edit/new,
    variable:mailto
    value:tom@neuro-logic.com

    That should cause all your cron output for your account to be redirected
    to tom@neuro-logic.com.

    As I mentioned before, kcron is just a GIU way to specify your crontab
    file. From the command line, run the "crontab -l" command and you will
    see how kcron set up your crontab.

    - --
    Jerry Feldman <gaf@blu.org>
    Boston Linux and Unix user group
    http://www.blu.org PGP key id:C5061EA9
    PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9
    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)

    iD8DBQE/y5/b+wA+1cUGHqkRAox0AJ95Er67uRwGl7K+RhynPNmKwjKUMACghgxf
    PpS5H1aupRssuKCUofcwtBk=
    =l0Hp
    -----END PGP SIGNATURE-----

    -- 
    Check the headers for your unsubscription address
    For additional commands send e-mail to suse-linux-e-help@suse.com
    Also check the archives at http://lists.suse.com
    Please read the FAQs: suse-linux-e-faq@suse.com
    

  • Next message: Sean Rima: "[SLE] Re: SuSE 9.0 NTFS Read/Write"

    Relevant Pages

    • Re: Running DBI, ODBC in the crontab
      ... Run the following lines in both the command line and crontab: ... Any of the paths that are missing in cron ... This communication is issued by UBS AG or an affiliate by the ...
      (perl.dbi.users)
    • Re: [SLE] Cron job generates a strange error messages
      ... > This is what I meant about non-printable garbage characters. ... I usually create new cron jobs ... Looking at crontab tells me nothing but if I either ... correct it in kcron or crontab by the explained method, ...
      (SuSE)
    • SUMMARY: cron entry: nth day of every month?
      ... cron can not handle this with its own syntax. ... 21st but "command" only runs if the output of the "date" command ... What I would suggest is rather than embedding the logic in each script ... The answer is it is _not_ possible to control it only with crontab ...
      (Tru64-UNIX-Managers)
    • Re: Cron job question
      ... > From: root@somedomain.nl (Cron Daemon) ... You've made the classic mistake of confusing the system crontab ... extra column defining which user ID the command should be run as. ... any new cron jobs for any user (including root) and leave the system ...
      (freebsd-questions)
    • Re: [opensuse] Re: cron problems
      ... The exception is when your crontab line starts ... your ipdetect cron job really works, you might want to turn off job start ... Your crontab syntax itself is OK, ... userid in it, before the command, has just the command. ...
      (SuSE)