RE: Universe on XP (Personal Edition)

2004-04-23 Thread Eremenko, Sergey
this is proper sequence of shutting UV off
net stop uvtelnet
net stop universe
net stop hsrexec
net stop unirpc

this is proper sequence of starting UV up
net start universe
net start uvtelnet
net start unirpc
net start hsrexec

Sergey Eremenko

-Original Message-
From: Anthony Dzikiewicz [mailto:[EMAIL PROTECTED] 
Sent: Friday, April 23, 2004 11:31 AM
To: U2 Users Discussion List
Subject: Universe on XP (Personal Edition)


So, I am doing a kind of odd ball thing.  I wrote some UV Basic programs to
create batch files that are run via the scheduled tasks.  I don't want
Universe running on my machine all the time.  So, I created a couple of
'.bat' files to start and stop universe, which are also set up as scheduled
tasks.  For example, stopuv bat file is

NET STOP UniVerse Telnet Service
NET STOP UniVerse REXEC Service
NET STOP UniVerse Resource Service
NET STOP Uni RPC Service

This appears to work.  The messages come up as everything being successful.
I do a 'NET START'  to see the services running and it doesn't show any of
the Universe processes.  However, I then realize that I am still logged into
Universe in the PC and it is still alive and well.  Is this a bug ?  If I
exit the session and then retry it, I wont be able to log in.  Also, If I
stop Universe the gui way from the control panel, I get the same result.
Does this happen on all windows platforms ? What if I were shutting down to
perform a backup and yet people were still messing with the data.

Anthony




-- 
u2-users mailing list
[EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
-- 
u2-users mailing list
[EMAIL PROTECTED]
http://www.oliver.com/mailman/listinfo/u2-users


RE: Universe on XP (Personal Edition)

2004-04-23 Thread Eremenko, Sergey
OK. I've done some testing. It appears that your telnet connection to
localhost UV will stay alive until you will leave that connection. Even if
universe itself stopped, you still able to run simple commands like LISTU,
LISTF, so on. I think that if you want to perform smooth clean and
no-troubles UV shutdown, you MUST do it from outside of your existing
connection. For instance, you can initiate scheduled command to execute your
stopuv.bat by invoke of AT command from your telnet session. It will
means that stopuv.bat will execute in different content than your UV
telnet session. And in this case your telnet connection will be kicked out
for sure.
My $.02
Sergey Eremenko.

-Original Message-
From: Anthony Dzikiewicz [mailto:[EMAIL PROTECTED] 
Sent: Friday, April 23, 2004 1:14 PM
To: U2 Users Discussion List
Subject: RE: Universe on XP (Personal Edition)


I understand.  Im just testing this at the command line.  Here is the output
of the stop;

C:\SCRIPTSstopuv

C:\SCRIPTSnet stop uvtelnet
The UniVerse Telnet Service service is stopping.
The UniVerse Telnet Service service was stopped successfully.


C:\SCRIPTSnet stop universe
The UniVerse Resource Service service is stopping.
The UniVerse Resource Service service was stopped successfully.


C:\SCRIPTSnet stop hsrexec
The UniVerse REXEC Service service is stopping.
The UniVerse REXEC Service service was stopped successfully.


C:\SCRIPTSnet stop unirpc
The Uni RPC Service service is stopping.
The Uni RPC Service service was stopped successfully.


C:\SCRIPTStype stopuv.bat
net stop uvtelnet
net stop universe
net stop hsrexec
net stop unirpc

C:\SCRIPTS

XP has a 'thing' where you can do something like   run1.bat  run2.bat or
run1.bat || run2.bat
This says that the second command runs only if the first is not successful
or vice versa.

So, with this you could say stop and if it fails go to try again until it
stops.  The problem is that is coming back 'ok'. It would be nice to do a
'ps -ef | grep uv' , but I don't think there is a windows equivalent.

Anthony

 -Original Message-
From:   [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]  On
Behalf Of Tony Gravagno
Sent:   Friday, April 23, 2004 3:49 PM
To: 'U2 Users Discussion List'
Subject:RE: Universe on XP (Personal Edition)

I use the same technique for starting D3, mvBASE, IIS, and other services
form desktop shortcuts.  Stopping services with a kill um all, let God sort
um out macro like this can be problematic, it really depends on the
service, but it's a nice way to free resources.  You may see the command
window flash as a BAT is executed, but if something is wrong you won't be
able to catch the errors.

Depending on how thorough you want to be, I recommend writing more code so
that your U2 systems update a Windows file when they boot and shutdown.  You
can then use a script (WSH) from your BAT which verifies the status before
termination, maybe with a pause if the status is unexpected - like if users
are still logged-in or some other processes are running.

HTH,
Tony

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
On Behalf Of Anthony Dzikiewicz
Sent: Friday, April 23, 2004 11:31 AM
To: U2 Users Discussion List
Subject: Universe on XP (Personal Edition)


So, I am doing a kind of odd ball thing.  I wrote some UV Basic 
programs to create batch files that are run via the scheduled tasks.  I 
don't want Universe running on my machine all the time.  So, I created 
a couple of '.bat' files to start and stop universe, which are also set 
up as scheduled tasks. For example, stopuv bat file is

NET STOP UniVerse Telnet Service
NET STOP UniVerse REXEC Service
NET STOP UniVerse Resource Service
NET STOP Uni RPC Service

This appears to work.  The messages come up as everything being 
successful. I do a 'NET START'  to see the services running and it 
doesn't show any of the Universe processes. However, I then realize 
that I am still logged into Universe in the PC and it is still alive 
and well.  Is this a bug ?  If I exit the session and then retry it, I 
wont be able to log in.  Also, If I stop Universe the gui way from the 
control panel, I get the same result. Does this happen on all windows
platforms ? What if I were shutting down to perform a backup
and yet people were still messing with the data.

Anthony




--
u2-users mailing list
[EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users


--
u2-users mailing list
[EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users

-- 
u2-users mailing list
[EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
-- 
u2-users mailing list
[EMAIL PROTECTED]
http://www.oliver.com/mailman/listinfo/u2-users


RE: Universe on XP (Personal Edition)

2004-04-23 Thread Eremenko, Sergey
(I'm talking about UV / NT tandem - I'm not Unix guru)
Unfortunately, stopping of UV telnet service will not log users out; it will
just prevent future logons via telnet.
Untill tl_server.exe process (corresponded to your connection to local UV)
is not terminating by something, it will stay here and you will be able to
see. You'd better log this connection out from outside or just kill this
process.

Sergey Eremenko

-Original Message-
From: Anthony Dzikiewicz [mailto:[EMAIL PROTECTED] 
Sent: Friday, April 23, 2004 2:14 PM
To: U2 Users Discussion List
Subject: RE: Universe on XP (Personal Edition)


That's the problem. Telnet isn't being kicked out.  I am doing this
(start/stop) from the command line already.  No big deal though.  I just
thought it was kind of odd.  We run the 'real' system on unix and linux
where I don't have such troubles. Anthony

 -Original Message-
From:   [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]  On
Behalf Of Eremenko, Sergey
Sent:   Friday, April 23, 2004 4:20 PM
To: 'U2 Users Discussion List'
Subject:RE: Universe on XP (Personal Edition)

OK. I've done some testing. It appears that your telnet connection to
localhost UV will stay alive until you will leave that connection. Even if
universe itself stopped, you still able to run simple commands like LISTU,
LISTF, so on. I think that if you want to perform smooth clean and
no-troubles UV shutdown, you MUST do it from outside of your existing
connection. For instance, you can initiate scheduled command to execute your
stopuv.bat by invoke of AT command from your telnet session. It will
means that stopuv.bat will execute in different content than your UV
telnet session. And in this case your telnet connection will be kicked out
for sure. My $.02 Sergey Eremenko.

-Original Message-
From: Anthony Dzikiewicz [mailto:[EMAIL PROTECTED]
Sent: Friday, April 23, 2004 1:14 PM
To: U2 Users Discussion List
Subject: RE: Universe on XP (Personal Edition)


I understand.  Im just testing this at the command line.  Here is the output
of the stop;

C:\SCRIPTSstopuv

C:\SCRIPTSnet stop uvtelnet
The UniVerse Telnet Service service is stopping.
The UniVerse Telnet Service service was stopped successfully.


C:\SCRIPTSnet stop universe
The UniVerse Resource Service service is stopping.
The UniVerse Resource Service service was stopped successfully.


C:\SCRIPTSnet stop hsrexec
The UniVerse REXEC Service service is stopping.
The UniVerse REXEC Service service was stopped successfully.


C:\SCRIPTSnet stop unirpc
The Uni RPC Service service is stopping.
The Uni RPC Service service was stopped successfully.


C:\SCRIPTStype stopuv.bat
net stop uvtelnet
net stop universe
net stop hsrexec
net stop unirpc

C:\SCRIPTS

XP has a 'thing' where you can do something like   run1.bat  run2.bat or
run1.bat || run2.bat
This says that the second command runs only if the first is not successful
or vice versa.

So, with this you could say stop and if it fails go to try again until it
stops.  The problem is that is coming back 'ok'. It would be nice to do a
'ps -ef | grep uv' , but I don't think there is a windows equivalent.

Anthony

 -Original Message-
From:   [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]  On
Behalf Of Tony Gravagno
Sent:   Friday, April 23, 2004 3:49 PM
To: 'U2 Users Discussion List'
Subject:RE: Universe on XP (Personal Edition)

I use the same technique for starting D3, mvBASE, IIS, and other services
form desktop shortcuts.  Stopping services with a kill um all, let God sort
um out macro like this can be problematic, it really depends on the
service, but it's a nice way to free resources.  You may see the command
window flash as a BAT is executed, but if something is wrong you won't be
able to catch the errors.

Depending on how thorough you want to be, I recommend writing more code so
that your U2 systems update a Windows file when they boot and shutdown.  You
can then use a script (WSH) from your BAT which verifies the status before
termination, maybe with a pause if the status is unexpected - like if users
are still logged-in or some other processes are running.

HTH,
Tony

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Anthony Dzikiewicz
Sent: Friday, April 23, 2004 11:31 AM
To: U2 Users Discussion List
Subject: Universe on XP (Personal Edition)


So, I am doing a kind of odd ball thing.  I wrote some UV Basic 
programs to create batch files that are run via the scheduled tasks.  I 
don't want Universe running on my machine all the time.  So, I created 
a couple of '.bat' files to start and stop universe, which are also set 
up as scheduled tasks. For example, stopuv bat file is

NET STOP UniVerse Telnet Service
NET STOP UniVerse REXEC Service
NET STOP UniVerse Resource Service
NET STOP Uni RPC Service

This appears to work.  The messages come up as everything being 
successful. I do a 'NET START'  to see the services running and it 
doesn't show

RE: UniVerse 10 on Win2k3

2004-03-24 Thread Eremenko, Sergey
I can't agree - you MUST have antivirus real-time scanner on MS Win server.
But id does make sense to simply exclude folders with UV accounts from
real-time scan. It works like a charm, btw.

-Original Message-
From: Donald Kibbey [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, March 24, 2004 10:06 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: UniVerse 10 on Win2k3


A good reason would be that your have just put your server under the control
of some very cpu intensive software.  I've seen to many cases where our
networking guys cranked up Norton or some other anti virus product on the
database servers and brought them to their collective knees.  One of the
great problems with Windoze (IMHO) is that it presents a pretty and familiar
face.  This results in stuff running on servers that simply should not be
there (screen savers, anit viri scanners, games, etc).

I say, don't run that anti virus junk on my db server and I won't crank up
SQL server on your firewall or PDC!!


Don Kibbey
Financial Systems Manager
Finnegan, Henderson, Farabow, Garrett  Dunner LLP


 [EMAIL PROTECTED] 03/24/04 12:54PM 
-- 
u2-users mailing list
[EMAIL PROTECTED]
http://www.oliver.com/mailman/listinfo/u2-users