From: Nick Dokos <nicholas.dokos@hp.com>
To: Teemu Likonen <tlikonen@iki.fi>
Cc: emacs-orgmode@gnu.org, Sanjib Sikder <sanjibju2002@gmail.com>
Subject: Re: org back up
Date: Wed, 17 Oct 2012 15:36:42 -0400 [thread overview]
Message-ID: <5775.1350502602@alphaville.americas.hpqcorp.net> (raw)
In-Reply-To: Message from Teemu Likonen <tlikonen@iki.fi> of "Wed, 17 Oct 2012 22:08:46 +0300." <87zk3kq5kx.fsf@mithlond.arda>
Teemu Likonen <tlikonen@iki.fi> wrote:
> Sanjib Sikder [2012-10-18 00:32:00 +0530] wrote:
>
> > Even after 26th minute, there is no sign of the code in work. Is it that
> > $HOME is not allowed and I need to give full path ?
>
> Ah, I thought that you'd run it from your personal crontab. So yes,
> write paths from root's point of view.
>
[I replied to Sanjib privately on the grounds that it's OT for the list,
but let me add a couple of notes to this thread before we shut it off
as completely OT: cron issues are hardly germane to org.]
o Adding personal items to root-owned crontabs is a *bad idea* indeed.
o One should try the script by hand before trying to incorporate it into cron:
much easier to debug.
o cron operates in a restricted environment: just run `env' as a cron job to
find out what it knows (hint: not much).
o Quite apart from cron issues, the backup method in the script is
fundamentally flawed in my opinion: iiuc, it flattens the hierarchy,
so if you have org files with the same name in different directories,
only *one* will be saved into the backup directory - hardly a reliable
backup.
Nick
next prev parent reply other threads:[~2012-10-17 19:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-17 18:25 org back up Sanjib Sikder
2012-10-17 18:41 ` Teemu Likonen
2012-10-17 19:02 ` Sanjib Sikder
2012-10-17 19:08 ` Teemu Likonen
2012-10-17 19:26 ` Sanjib Sikder
2012-10-17 19:41 ` Teemu Likonen
2012-10-17 19:36 ` Nick Dokos [this message]
2012-10-17 19:38 ` Sanjib Sikder
2012-10-18 0:14 ` Suvayu Ali
2012-10-17 19:25 ` Achim Gratz
2012-10-17 20:05 ` Russell Adams
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5775.1350502602@alphaville.americas.hpqcorp.net \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=sanjibju2002@gmail.com \
--cc=tlikonen@iki.fi \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).