I always just set MAXUSR to 0, and then walked around the company and logged everyone off who had gone home without logging out.
Oh, yeah, that was PRIMOS, twenty years ago. And it only worked for the remote branches if I could find someone working late there, or the janitor, to log terminals out. -- Louie On 9/17/07, Norman Morgan <[EMAIL PROTECTED]> wrote: > > So, what is the best way to log users off cleanly in mass? You > certainly can't depend on users to log off for themselves. Asking, > begging, threatening....none of that works. I know for certain if I log > in at 03:00, there will be 15 to 20 users still logged in, even though > the building has been empty for hours. > > =========================================================== > Norman Morgan <> [EMAIL PROTECTED] <> http://www.brake.com > =========================================================== > Sometimes I wake up grumpy. Other times I let her sleep. > =========================================================== > > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of > > Timothy Snyder > > Sent: Monday, September 17, 2007 3:09 PM > > To: [email protected] > > Subject: Re: [U2] UniVerse and Shadow copy on Windows 2003 > > > > > The only way to guarantee business level data integrity in > > non-transactional > > > applications is to force all users off the system briefly > > while you do > > steps > > > 1 - 3. > > > > That's a good point. However, it's important to have a > > controlled way to do so. I've had people think they were > > safe to just log everybody off. Of course, there's no way to > > ensure you're not doing *that* in the middle of a transaction. ;-) > > > > Much worse, I've even had people with good intentions of > > getting everybody off of the system so they could have stable > > backups. How did they do it? > > With stopud -f or by doing a kill -9 on each user. Either > > one could create a mess at least as bad as backing up hot, > > since processes are not terminated cleanly. Actually, the > > mess could be worse with the unconditional kill methods, > > since they could result in corruption of the live database > > files, while backing up hot only impacts the backup copy. > > And if you do that while running RFS, head for the hills. > > > > Tim Snyder > > Consulting I/T Specialist > > U2 Lab Services > > Information Management, IBM Software Group > > ------- > > u2-users mailing list > > [email protected] > > To unsubscribe please visit http://listserver.u2ug.org/ > ------- > u2-users mailing list > [email protected] > To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
