rrd-status.log errors and df output of SunOS client

[Dominique Frise]

Hi,

Our rrd-status.log is filled with errors like:

2006-04-18 10:50:39 RRD error updating 
/soft/pub/BB/hobbit/data/rrd/host1/disk,swap.rrd from 1.2.3.4: illegal attempt 
to update using time 1145350239 when last update time is 1145350239
(minimum one second step)

----corresponding client data----
[df]
Filesystem            kbytes    used   avail capacity  Mounted on
nfs:/soft/lic/sun    10317828 8199048 1594664    84%    /soft/lic/sun
swap                 17835128      64 17835064     1%    /var/run
swap                 3145728    4624 3141104     1%    /tmp
/dev/md/dsk/d0       5046030 4150823  844747    84%    /
/dev/md/dsk/d3       25215720 5327869 19635694    22%    /var
/dev/md/dsk/d4       15128715 9697901 5279527    65%    /usr/local
----------------------------------


The two swap entries (/tmp and /var/run) are probably creating this problem?
If this is the case /var/run should be excluded from the df output in 
hobbitclient-sunos.sh
The mounted file system (nfs) should also be excluded (use -l option of df)


Under Solaris 10, following FS types should additionaly be excluded:

ctfs - contract file system
      The ctfs filesystem is the interface to  the  contract  sub-
      system. ctfs is mounted during boot at /system/contract. For
      information on contracts and the contents of  this  filesys-
      tem, see contract(4).

devfs - Devices file system
      The devfs filesystem manages a name  space  of  all  devices
      under  the Solaris operating environment and is mounted dur-
      ing boot on the /devices name space.

      The /devices name space is dynamic and reflects the  current
      state  of  accessible  devices  under  the Solaris operating
      environment. The names of all attached device instances  are
      present under /devices.

      The content under /devices is under the exclusive control of
      the devfs filesystem and cannot be changed.

objfs - Kernel object filesystem
      The objfs filesystem describes  the  state  of  all  modules
      currently loaded by the kernel. It is mounted during boot at
      /system/object.

      The contents of the filesystem are dynamic and  reflect  the
      current state of the system. Each module is represented by a
      directory containing a single  file,  'object.'  The  object
      file  is  a  read  only  ELF file which contains information
      about the object loaded in the kernel.



Dominique