Hugh E Cruickshank wrote:
The problem I have with that is amount of effort that will take to "sell", implement and support the solution. I can make recommendations but that does not mean that they will be automatically accepted. If I have to spend that much effort on what is essentially a "stop gap" measure until we implement a ticketing system I might as well spend the time on the final solution. All I was really looking for was something that might ease the efforts I am currently expending to support the current "stop gap" measure. If that is not possible then I will have to live with things the way they are until we can proceed to the next level (i.e. a ticketing system).
You can't get much easier than files containing a list of the right delivery addresses for each time period and a cron job that copies the right file to the one :included: by a sendmail alias at each transition. Did you try that approach yet? But for ongoing things you lose the ability to easily see what the previous shift did unless they reply/forward a copy of anything still needing work.
-- Les Mikesell lesmikesell@xxxxxxxxx _______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos
