Project

General

Profile

Bug #19454

warn users that crontab is not supported

Added by Ash Gokhale about 3 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
Nice to have
Assignee:
Warren Block
Category:
Documentation
Target version:
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

As seen in EZQ-441-20778:

Upgrades will not preserve crontab entries entered with unix 'crontab'; so put a warning about it in the default crontab.

Given this information, I have a feature request for the dev team. Can you
ask them to install a default crontab for root that basically contains a
message that it's managed by TrueNAS and shouldn't be edited directly by
end users. I'm thinking something along the lines of the message that
Network Manager places in resolv.conf on Linux.

Let me know if it's better for me to file a separate ticket with this
feature request in it.

Thanks!

History

#1 Updated by Josh Paetzel about 3 years ago

Put that message in every config file there is?

#2 Updated by Heather Ownby about 3 years ago

  • Assignee set to Dru Lavigne

#3 Updated by Dru Lavigne about 3 years ago

  • Category changed from Documentation to 3
  • Assignee changed from Dru Lavigne to Kris Moore

#4 Avatar?id=14398&size=24x24 Updated by Kris Moore about 3 years ago

  • Status changed from Unscreened to 15

Yea, once we go down this path, where does it end? Every *.conf file in /etc? /usr/local/etc/?

I'm inclined to pass on this one for now, especially if we aren't doing something wrong to direct users to the crontab utility in the docs or help text somewhere.

#5 Updated by Glen Gibb about 3 years ago

I'm the user who submitted the feature request to Ash. I was asking for it primarily for crontab, although I can see the argument for applying it to other config files.

My reason for requesting it on root's crontab (/var/cron/tabs/root ?) is that it's pretty common for a sysadmin to run the crontab command and manually edit the file. When we performed an OS update, the crontab contents were lost.

There's actually no indication in the TrueNAS manual (9.10 sec 5.1 and 9.3 sec 6.1 both have similar wording) that you shouldn't use the crontab command line utility to manage this:

cron(8) is a daemon that runs a command or script on a regular schedule as a specified user. Typically, the user who wishes to schedule a task manually creates a crontab(5) using syntax that can be perplexing to new Unix users. The TrueNAS® GUI makes it easy to schedule when the task will occur.

#6 Avatar?id=14398&size=24x24 Updated by Kris Moore about 3 years ago

  • Category changed from 3 to Documentation
  • Assignee changed from Kris Moore to Dru Lavigne
  • Target version set to 9.10.2-U1

Dru - Could we just clarify in that doc section that the crontab file should not be hand-edited outside of the UI?

#7 Updated by Dru Lavigne about 3 years ago

  • Status changed from 15 to Screened
  • Assignee changed from Dru Lavigne to Warren Block

#8 Updated by Warren Block almost 3 years ago

  • Status changed from Screened to Resolved

User guide updated.

#9 Updated by Dru Lavigne almost 3 years ago

  • Priority changed from No priority to Nice to have
  • Target version changed from 9.10.2-U1 to 9.10.2

Also available in: Atom PDF