# Generally, if you want all your users to provide a service for your # benefit but want them to be able to override your default setting, # you should put it in this file but not use quit. Eg: # if ( grep service-user-shell /etc/shells # & glob service mail-delivery # & glob calling-user mail # ) # reset # no-suppress-args # execute /usr/local/bin/procmail-wrapper # fi # (procmail-wrapper could extract envelope information from the # arguments and/or -D options and pass them to procmail.) include-directory /etc/userv/default.d include-lookup service /etc/userv/services.d # If you want to force users to provide a particular service, # then you can put it here and use `quit'. Eg: # if ( grep service-user-shell /etc/shells # & glob service cleanup-tmp # ) # reset # errors-to-syslog local4 # execute /usr/local/bin/cleanup-tmp # no-set-environment # no-disconnect-hup # null-fd 0 read # null-fd 1-2 write # quit # fi # Alternatively, you could put the same thing in system.override, with # or without the quit. In this case it's usually important to use # reset, and also to note that now users can cause error messages # which they could not do before (though due to the implied catch-quit # around the user's rc file they wouldn't stop the service being # executed). # # If you want to force all your users' services to have a particular # property you should do it in system.override. Eg, there put # set-environment # to force them to run /etc/environment to have ulimits set up, even # if they try not to. # # NB that doing this _won't_ affect things in system.default and # earlier in system.override that use `quit'.