Is fstab-sync in newest cvs broken?

[David Zeuthen]

On Thu, 2004-08-26 at 23:36 +0200, Thomas Gufler wrote: 
> > So, you said you were using the CVS version? Would that be hal-cvs from
> > Gentoo (I'm just guessing)?
> Yes, you are right.
> 

OK, good to know.

> >
> > In that case please ensure you configure the sources with --enable-
> > verbose-mode. Or even better, run the code directly from a CVS
> > checkout :-)
> >
> Ok, now I get a lot more:
> See output_hald_new
> 

What I get looks like this

        [root at laptop hald]# ./hald --daemon=no
        23:37:42.070 [D] hald.c:317: opt_become_daemon = 0
        23:37:42.222 [I] linux/osspec.c:194: Mountpoint for sysfs is /sys
        23:37:42.403 [I] linux/osspec.c:1223: ******************************************
        23:37:42.403 [I] linux/osspec.c:1224: **** hotplug_counter is now 1
        23:37:42.403 [I] linux/osspec.c:1225: ******************************************
        23:37:42.495 [I] callout.c:332: Invoking 40-hal-hotplug-map.hal
        23:37:42.894 [I] callout.c:332: Invoking 50-fstab-sync.hal
        19385: ###################################
        19385: fstab-sync entering; add udi=/org/freedesktop/Hal/devices/computer
        19385: mount_root=/media use_managed=yes managed_keyword=kudzu
        19385: Acquiring advisory lock on /etc/fstab
        19385: Lock acquired
        19385: Releasing advisory lock on /etc/fstab
        19385: Lock released
        19385: fstab-sync exiting; add udi=/org/freedesktop/Hal/devices/computer
        19385: ###################################
         
        23:37:43.277 [I] hald.c:73: Added device to GDL; udi=/org/freedesktop/Hal/devices/computer
        
the CVS version of hald passes HALD_VERBOSE=1 to the callouts if verbose
mode is set; and the CVS version of fstab-syncs check for this 

(in fact the fstab-sync callout cleans the fstab on computer add and
HALD_INIT is set to TRUE (but only, of course, if configured with --
enable-mnt-op e.g. we're using a kudzu or managed keyword)).

So, judging from your output it would appear that callouts are never
run; after configuring hal the configure script prints out some
information, in particular this line

  sysconfdir:               /usr/local/etc

What does your ${sysconfdir}/hal/device.d look like are where do the
symlinks point to and what are the timestamps on the targets?

Thanks,
David

_______________________________________________
hal mailing list
hal at freedesktop.org
http://freedesktop.org/mailman/listinfo/hal