For such a platform, a SeD configuration file could be:
| # file SeD_example.cfg, configuration file for a SeD | |||
| parentName | = | LA_example | |
| #traceLevel | = | 1 | # default |
| #dietPort | = | <port> | # not needed |
| #dietHostname | = | <hostname|IP> | # not needed |
| fastUse | = | 1 | |
| ldapUse | = | 1 | |
| ldapBase | = | ldaphost:9000 | |
| ldapMask | = | dc=LIP,dc=ens-lyon,dc=fr | |
| nwsUse | = | 1 | |
| nwsNameserver | = | nwshost:9001 | |
| #useLogService | = | 0 | # default |
| #lsOutbuffersize | = | 0 | # default |
| #lsFlushinterval | = | 10000 | # default |
The SeD will register as a child of LA_example. Run the executable that you linked with the DIET SeD library, and do not forget that the first argument of the method call diet_SeD must be the path of the configuration file above.