Bug 14620 - motd is invaild paramater in rsyncd.conf
Summary: motd is invaild paramater in rsyncd.conf
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-20 18:41 CET by james Whitby
Modified: 2014-11-21 03:08 CET (History)
0 users

See Also:
Source RPM: rsync-3.1.1-4.mga5.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description james Whitby 2014-11-20 18:41:30 CET 
Description of problem:
rsyncd.conf contains:
motd = /var/tmp/welcome.msg

Syslog has:
rsyncd[23287]: Unknown Parameter encountered: "motd"


Version-Release number of selected component (if applicable):
3.1.0 and 3.1.1

How reproducible:
Add motd to rsyncd.conf.
Run rsync as a daemon.
Check syslog.



Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:
Comment 1 David Walser 2014-11-20 23:12:15 CET 
The rsyncd.conf in the package doesn't have that.  You must have put that there yourself.

Status: NEW => RESOLVED
Resolution: (none) => INVALID

Comment 2 james Whitby 2014-11-21 02:11:36 CET 
hmmm.... 

snippet from man rsyncd.conf:

      motd file
              This parameter allows you to specify a "message of the  day"  to
              display  to  clients on each connect. This usually contains site
              information and any legal notices. The default is no motd  file.
              This  can  be  overridden  by  the  --dparam=motdfile=FILE  comâ
              mand-line option when starting the daemon.

Status: RESOLVED => REOPENED
Resolution: INVALID => (none)

Comment 3 james Whitby 2014-11-21 03:08:16 CET 
MY error!

The paramater should be:
motd file = <filename>

Misreading the man page!

Found my error reqading the loadparm.c file.

Pardon the noise.

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.