Subject: | |
From: | |
Reply To: | |
Date: | Mon, 18 Jan 1999 12:57:03 -0500 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Chris and Patrick
Also from MPEiX you can;
:PURGELINK UDCFILE
:RENAME NEWUDC,UDCFILE
John Zoltak
North American Mfg Co
-----Original Message-----
From: Chris Bartram [mailto:[log in to unmask]]
Sent: Monday, January 18, 1999 12:31 PM
To: [log in to unmask]
Subject: [HP3000-L] Re[2]: setcatalog hassle (was: hpprompt -Reply)
In <[log in to unmask]> [log in to unmask] writes:
> > If the "setcatalog hassle" refers to the problem of not being able
to
> > edit the UDC file as long as it is still "in use" by some users
logged
> > on, then the following "trick" might be helpful...
> >
> > :/bin/mv "UDCFILE OLDUDC"
> > :/bin/mv "NEWUDC UDCFILE"
>
> Does "mv" work differently than "RENAME"? If not, I don't think this
> will work. If so, what does "mv" do differently, and why the heck
don't
> we have the same functionality with "RENAME" ???
Posix' "mv" command does work differently than rename. I use the above
trick
all the time to "rename" udc files (and even program files) that are in
use
so I can replace them for subsequent openers.
From mpe;
:MV.HPBIN.SYS "UDCFILE OLDUDC"
:RENAME NEWUDC,UDCFILE
mv works even on files that are in use (just like Posix' "rm" can delete
a file that's in use - unlike :PURGE).
We even use the mv "trick" in our NetMail/3000 update scripts to allow
updates to be done without even making everyone "get out" of the
application.
"Works great. Lasts long time."
-Chris (remove nospam) Bartram
|
|
|