Re: [Bug 1532999] Re: cron does not read $PATH or Gnome Schedule doco is insufficient
Humphrey van Polanen Petel writes on January 14, 2016 4:20: > re cron -- how do I raise this as a bug/feature request? Look for the implementation of cron you are using (dcron?) then search for them, I do not know, they are completely separete from gnome-schedule. Maybe google a little about why it is like this first, because it is likely to be a concious choice. > re Gnome Scedule doco -- sorry, but writing docs is serious business and > I know too little about what is going on > > re general doco -- I will just keep plodding along > > Anway, thank you, Gaute Sure! There are a bunch of concepts that are unfamiliar in the beginning, but they are usually consistent along how Linux and friends work. So once you get started new things will go easier. - gaute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532999 Title: cron does not read $PATH or Gnome Schedule doco is insufficient To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-schedule/+bug/1532999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1532999] Re: cron does not read $PATH or Gnome Schedule doco is insufficient
Humphrey van Polanen Petel writes on January 13, 2016 0:35: > Yes, it now works as it should. Thanks. > > But, my original complaint still stands: > > 1 - cron does not read $PATH, but should. There are secuirty reasons and other implementation difficulties for that, usually it is not a big problem. Anyway, it is a bug/feature-request for cron. > 2 - Gnome Scedule doco is insufficient. Docs can always be better, and adding some additional information on how cron works could be useful. If you make a patch I would be happy to review it. > As a side comment, I do know that coming to Linux incurs a steep > learning curve, but what I have seen of it so far tells me that the > learning curve would be a lot less steep if it the documentation were > to be improved. Yes, some of it comes from the ancient ways nix works. The command line is very powerful, but it also offers lots of possibilities for using it incorrectly. Perhaps some more examples in the docs would help, I hardly remember anymore if there are any (although it is not the responsibility of gnome-schedule to teach general linux and shell commands, that would bloat the docs with irrelevant stuff). Happy it works. Gaute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532999 Title: cron does not read $PATH or Gnome Schedule doco is insufficient To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-schedule/+bug/1532999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1532999] Re: cron does not read $PATH or Gnome Schedule doco is insufficient
Ok. It would not work with just 'bup' since cron does not read $PATH. Also, tail -f /var/mail/humphrey does not clear the previous log so you would get the same error every time in your log file, even though the command works correctly. A better way is: /usr/local/bin/bup > /path/to/logfile 2>&1 Could you please try that, and see if it works correctly now. Indeed, using '&&' results in the old log (from the mail) only being copied over if the first command succeeds. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532999 Title: cron does not read $PATH or Gnome Schedule doco is insufficient To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-schedule/+bug/1532999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
