It works! It simply works this way. The error which is thrown is somewhat
ugly. addmount is used to automatically edit the fstab and add the nfs
mountpoint and to mount the nfs filesystem. All the samples are using
the sequence mountall, addmount, mountall. The second mountall seems
to be misplaced if addmount does the mounting of the missing
filesystems, right?
In order to show the context I will include the correct cfagent.conf
file below.
@mark: this is documentated in a strange way. If I am writing a small
explanation to the miscmount section and contribute a small sample to
it, will you include it in the documentation?
Cheers
Uli
===== Working cfagent.conf =====
control:
actionsequence = (
mountall
addmounts
)
[....config stuff....]
miscmounts:
server.example.com:/mnt/nfs /mnt/nfs-test mode=ro
This error message is totally unclear to me.
I used "addmounts" as the only command in action sequence. If the
mountpoint isn't defined in /etc/fstab, addmounts adds it and keeps
quiet about it.
If I run cfagent -v for the second time, addmounts(!) throws "your" error
message. If I understood addmounts correctly, it doesn't try to mount
the filesystem, but only checks if all mountables are in /etc/fstab and
adds them if not.
mountall then mounts the filesystem just fine.
I haven't the faintest idea, why *addmounts* throws this message.
Regards,
Ralph
--
Ralph Angenendt......ra@br-online.de | .."Text processing has made it possible
Bayerischer Rundfunk...HA-Multimedia | ....to right-justify any idea, even one
Rundfunkplatz 1........80300 München | .which cannot be justified on any other
Tl:089.5900.16023..Fx:089.5900.16240 | ..........grounds." -- J. Finnegan, USC
Hi all, We are currently setting up our cfengine software. We seem to be having some strange behaviour with regards to the sysadm directive. We have found that the mailing address prepends "cfengine@" onto the front of a define mail address. The output is as follows, with the anomaly in bold red. Have we made a fundamental mistake somewhere? We have looked closely at examples and checked the reference guide, but to no avail. Is this a bug? Glen ---------------------------------------------------------------------Starting server
**********************************************************************
This message is intended for the addressee named and may contain
privileged information or confidential information or both. If you
are not the intended recipient please delete it and notify the sender.
**********************************************************************