I must fully qualifty..... this post got long.
This has been a lingering problem for me. If you've got a few minutes, feel free to reply, because I'm stumped and AIX support basically told me this isn't possible. But it happens on several of my machines!
Here is the issue:
I have several rs6000s still running 4330-11. When a print queue goes down (typically because an NT print server is down), and a job is sent at the exact same time from the 6000 via user1... the job will sit in a down queue, waiting for the queue to come back up. That's what we want, right?
So if the NT print server doesn't come back up, and I try to bring the AIX queue up (via a ksh script running in cron ever 30 mins) AIX wants to send or tell user1 or root a message letting us know it couldn't bring the queue up.
Here is the process the os follows to notify user1 or root when the queue fails to come back up.
1. Is user1 logged on? if yes, then display to user1's screen, else go to 2.
2. Is root logged on? if yes, then display to root's screen, else go to 3.
3. Is the scsi attached terminal toggled to this rs6000? If yes, then display on terminal screen, else go to 4.
4. Send an email to user1's $HOME/.forward
The problem is when we get to step four ( nobody is logged on and the scsi monitor (ibm 3153) is toggled to a different 6000.... user1 gets an email. The real problem is the programmers use the .forward in all there scripts to email all the users on this application....( i know this is stupid) so /home/user1/.forward emails several hundred people about this down print queue. It's a mess.
Can I turn the functionality of notifying user1 or root off? I want to bring the queues up, but I really don't care if they don't come back up
This has been a lingering problem for me. If you've got a few minutes, feel free to reply, because I'm stumped and AIX support basically told me this isn't possible. But it happens on several of my machines!
Here is the issue:
I have several rs6000s still running 4330-11. When a print queue goes down (typically because an NT print server is down), and a job is sent at the exact same time from the 6000 via user1... the job will sit in a down queue, waiting for the queue to come back up. That's what we want, right?
So if the NT print server doesn't come back up, and I try to bring the AIX queue up (via a ksh script running in cron ever 30 mins) AIX wants to send or tell user1 or root a message letting us know it couldn't bring the queue up.
Here is the process the os follows to notify user1 or root when the queue fails to come back up.
1. Is user1 logged on? if yes, then display to user1's screen, else go to 2.
2. Is root logged on? if yes, then display to root's screen, else go to 3.
3. Is the scsi attached terminal toggled to this rs6000? If yes, then display on terminal screen, else go to 4.
4. Send an email to user1's $HOME/.forward
The problem is when we get to step four ( nobody is logged on and the scsi monitor (ibm 3153) is toggled to a different 6000.... user1 gets an email. The real problem is the programmers use the .forward in all there scripts to email all the users on this application....( i know this is stupid) so /home/user1/.forward emails several hundred people about this down print queue. It's a mess.
Can I turn the functionality of notifying user1 or root off? I want to bring the queues up, but I really don't care if they don't come back up