Chandra Seetharaman wrote: > By default, class is inherited by forked children. So, your requirement > can be satisfied if you could attach the login shell to a class based on > the userid at the time of login, then (all tasks started by) the user > will be attached to the class. This can be achieved by writing a shell > script and executing it as part of .login. > I had already thought of something along these lines. However, AFAIK, /etc/profile and such files will be executed as the user logging in, so I would have to either:
a) Give, somehow, write access for everybody to the configfs (clearly undesirable, since user could mess with priorities and reclassify themselves/others). b) Make some kind of setuid script to do the classification (and it would be a kludge anyway), which, even if doable, doesn't seem too desirable either. I am not aware of any startup file executed when a user logs in before setting uid to the user, because that would be the right place to do that. Another option would be a daemon running in background and searching periodically (e.g. each minute or so) for tasks not yet classified (i.e. in the root class) and sending each one it finds there to the right place... Would be useful only for longer jobs that doesn't end before the daemon gets them (the ones we are interested in, anyway). Anyway, I'll think a bit more about it and post any solution I finally find (suggestions most welcome ;) ). Thanks, Joan _______________________________________________ ckrm-tech mailing list https://lists.sourceforge.net/lists/listinfo/ckrm-tech
