Actions
User story #3092
closeddocument usage of Enforce a file content Technique
Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Documentation
Target version:
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:
Description
Given i am a Rudder user.
Explain usage of Enforce a file content Technique witn an example.
I want to configure a /etc/backupninja.conf, which must contain following lines, but not necessary in a block with the same order:
loglevel = 4 reportemail = root reportsuccess = yes reportinfo = no reportwarning = yes reportspace = no reporthost = backup.$COMPANY.TLD$ reportuser = ninja-$HOSTNAME$ reportdirectory = /var/lib/backupninja/reports/$HOSTNAME$
Question Nr1: How is managed the "Section: File content" ? How do i enforce a block of text ? How do i enforce independent lines ?
Question Nr2: $HOSTNAME$ is certainly a variable somewhere, where do I find the list of accessible variables.
Updated by Benoît PECCATTE almost 10 years ago
- Project changed from 30 to Rudder
- Category set to Documentation
Updated by Benoît PECCATTE over 8 years ago
- Target version set to Ideas (not version specific)
Updated by Alexis Mousset over 6 years ago
- Status changed from New to Rejected
Started in Rudder by example, closing.
Actions