>C. If I disable the application, then do a 'disable -t' on it, then reboot, >the application does NOT start following the reboot [not as I expected].
It is disabled; "disable -t" also temporarily disable it (a NO-OP). So it remains disabled. So what you are looking for is "enable on next boot". > .general_ovr/enabled boolean false > .general/enabled boolean false > .general/entity_stability astring Stable > .general/single_instance boolean true > >So, what else has to be set so that the application is started following the >reboot? I am at a los s to understand the difference between doing a 'disable -t' on an enabled application vs. doing tha t on a disabled application. I think it's setting general/enanbled which addresses that (but it would be nice if there was a supported command for "enable/disable" on next boot) Casper
