Dhaval,
Thanx for replay.
It seems like my issue was related to missing kernel Connector module. Loading
it before daemon launch solves issue. I think it will be good to add small
checks at daemon startup for informing user about missing environmental
components.
Speaking with You - I have small q:
I understand cgrulesengd daemon moves tasks to appropriate groups when:
1.task is changing it's UID/GID (daemon uses events from the kernel).
2.PAM is used during task launch.
So first case - from userspace perspective - means task should be launched via
suexec().
If my app is using following commands to launch tasks:
/* Run command */
execl("/bin/sh", "sh", "-c", cmdargs, (char *)0);
will it be properly clasified by cgrulesengd ?
Thx in advance !
------------------------------------------------------------------------------
Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL,
new data types, scalar functions, improved concurrency, built-in packages,
OCI, SQL*Plus, data movement tools, best practices and more.
http://p.sf.net/sfu/oracle-sfdev2dev
_______________________________________________
Libcg-devel mailing list
Libcg-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libcg-devel
