From: Jouni Kosonen <jouni.kosonen@tukesoft.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: crontab backup
Date: Wed, 17 Sep 2014 05:22:27 +0300 [thread overview]
Message-ID: <lvar93$imp$1@ger.gmane.org> (raw)
In-Reply-To: 20140917013036.GC7543@syscon7
Joseph wrote:
> I'm trying to backup crontab from various boxes to files, so I'm using
> (run once a month) 11 01 * * 5 crontab -l >
> /home/joseph/business/backup/crontabs/syscon7_joseph_crontab
>
> but I can from bash: cannot overwrite existing file
>
From "man bash":
Redirecting Output
...
If the redirection operator is >, and the noclobber option to the
set builtin has been enabled, the redirection will fail if the file
whose name results from the expansion of word exists and is a regu‐
lar file. If the redirection operator is >|, or the redirection
operator is > and the noclobber option to the set builtin command
is not enabled, the redirection is attempted even if the file named
by word exists.
---
Jouni
next prev parent reply other threads:[~2014-09-17 2:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 1:30 [gentoo-user] crontab backup Joseph
2014-09-17 2:22 ` Jouni Kosonen [this message]
2014-09-17 2:57 ` [gentoo-user] " Joseph
2014-09-17 8:43 ` [gentoo-user] " Neil Bothwick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='lvar93$imp$1@ger.gmane.org' \
--to=jouni.kosonen@tukesoft.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox