Grossd won't start if statefile enabled in Ubuntu 10.10 and Gross 1.0.2-2 about gross HOT 5 CLOSED

Does gross (user) have write permission to /var/lib/gross directory? Try 
creating /var/db/gross (or something similar), and then give write permission 
to gross user to that directory. Then, configure statefile to be created in 
that directory and run grossd -C.

However, I don't see how statefile creation could fail without grossd 
complaining. (Statefile is created in create_statefile() function in srvutils.c)

The gross user has write permissions to /var/lib/gross, as shown by
results of the above line '6. sudo ls
-la /var/run/gross/gross.pid /var/lib/gross'.

I did create /var/db/gross and chown'ed it to gross and the
results were are the same.

It seems to be related with the following line in file src/gross.c:
    if ((ctx->config.flags & FLG_CREATE_STATEFILE) ==
FLG_CREATE_STATEFILE) {

Otherwise we should be seeing some output from:
        } else {
            daemon_shutdown(EXIT_FATAL, "statefile not
configured");


Anyway I think that, for now, we will abandon Gross.
It follows a nice idea, but at least in Linux it does not seem to be
mature enough and does not justify the time lost with it.


Best wishes,

M.

Could you please run grossd -C with strace and send me the output? You can mail 
the trace to me directly if you are not comfortable to attach it here.

Also, I'd be grateful if you told me what you think is not "mature enough in 
Linux". I ask because I'm not aware of any current stability issues.

[SOLVED] please close ticket.

The Ubuntu Gross .deb package postinst uses 'install -d -o gross -g gross -m 
0700 /var/lib/gross' to create the /var/lib/gross directory in which the 
statefile should be stored.

In Ubuntu (at least with with apparmor on and using strict permissions 
enforcement), one must assure that sudoers & apparmor are configured to permit 
'sudo -u gross /usr/sbin/grossd -C' to use the /var/lib/gross directory.

Great that you found a solution.