Two observations:
1. Do you have permission to the directory you are trying to create a file? Your $I pathis different than the MYIO path.
2. All the comments about $T value after doing an OPEN command are meaningless. The OPEN command is suppose to set $T only if you use OPEN with a timeout. I
On Jul 16, 2006, at 3:15 PM, Steven McPhelan wrote:2. All the comments about $T value after doing an OPEN command are meaningless. The OPEN command is suppose to set $T only if you use OPEN with a timeout. I did not see where any one used an OPEN command with a timeout.You're right. Taking a
On Jul 16, 2006, at 5:00 PM, Gregory Woodhouse wrote:It's sensible that an attempt to open a device that is busy should block, but what if the OPEN cannot succeed on semantic grounds (e.g., an attempt to open a connection to a non-routable address)? It seems to me that raising an error ought to be
(substitute the actual file name for /tmp/file.txt):
S MYIO=/tmp/file.txt
O MYIO W $T
C MYIO
GTMS MYIO=/home/myvista/testIO.txt
GTMO MYIO W $T
1
GTMC MYIO
GTMH
[EMAIL PROTECTED]:~/foia06152006$ ls -la ~/testIO.txt
-rw-r--r-- 1 myvista myvista 0 2006-07-09 23:21 /home/myvista/testIO.txt
On Jul 10, 2006, at 1:10 AM, Ismet Kursunoglu wrote:(substitute the actual file name for /tmp/file.txt):S MYIO="/tmp/file.txt"O MYIO W $TC MYIO GTMS MYIO="/home/myvista/testIO.txt"GTMO MYIO W $T1GTMC MYIOGTMH[EMAIL PROTECTED]:~/foia06152006$ ls -la ~/testIO.txt-rw-r--r-- 1 myvista myvista 0
That was dumb of me!
GTMS MYIO=/home/nancy/testIO.txt
GTMO MYIO W $T
1
GTMC MYIO
On Monday 10 July 2006 00:56, chuck5566 wrote:
Nancy,
On Jul 9, 2006, at 11:26 PM, Nancy Anthracite wrote:
I tried playing with it:
GTMS MYIO=home/nancy/testIO.txt
I'm curious - (if you get time) would it
It looks to me like the Kernel Systems Manual found at www.va.gov/vdl under
Infrastructure, Kernel, in the section Taskman System Management (section 22)
might help.
On Monday 10 July 2006 04:10, Ismet Kursunoglu wrote:
(substitute the actual file name for /tmp/file.txt):
S
Kursunoglu [EMAIL PROTECTED]
To: hardhats-members@lists.sourceforge.net
Sent: Monday, July 10, 2006 4:10 AM
Subject: Re: [Hardhats-members] sshd and mumps process hung
(substitute the actual file name for /tmp/file.txt):
S MYIO=/tmp/file.txt
O MYIO W $T
C MYIO
GTMS MYIO=/home/myvista
@lists.sourceforge.net
Sent: Monday, July 10, 2006 4:10 AM
Subject: Re: [Hardhats-members] sshd and mumps process hung
(substitute the actual file name for /tmp/file.txt):
S MYIO=/tmp/file.txt
O MYIO W $T
C MYIO
GTMS MYIO=/home/myvista/testIO.txt
GTMO MYIO W $T
1
GTMC MYIO
GTMH
S MYIO=/home/myvista/testIO.txt
O MYIO
U MYIO W !,Hello there!
C MYIO
Then, go ahead and check the contents of the file.
[EMAIL PROTECTED]:~$ cat testIO.txt
Hello there!
No matter how I setup the HFS device it continues to show
[DEVICE IS BUSY]
I suspect that Kernel is not
Sorry guy, I dont know anything about *nix nor the non-FOIA releases of VistA.
Seems like somebody on a *nix system could send you a global output of
their DEVICE file. That may at least get the HFS issue ironed out.
At 05:35 PM 7/10/2006, Ismet wrote:
S MYIO=/home/myvista/testIO.txt
O
Sorry, I probably misled you in saying that ZISFGTM would work properly as
^%ZISF. It worked for me because I used OPEN PARAMETERS in the HFS device
definition, thereby bypassing a problematic part. However, the following
change to ^%ZISF (_ZISF.m) works for asking mode.
Insert a line
Subject: Re: [Hardhats-members] sshd and mumps process hung
(substitute the actual file name for /tmp/file.txt):
S MYIO=/tmp/file.txt
O MYIO W $T
C MYIO
GTMS MYIO=/home/myvista/testIO.txt
GTMO MYIO W $T
1
GTMC MYIO
GTMH
[EMAIL PROTECTED]:~/foia06152006$ ls -la ~/testIO.txt
-rw-r
[EMAIL PROTECTED]
To: hardhats-members@lists.sourceforge.net
Sent: Monday, July 10, 2006 1:10 AM
Subject: Re: [Hardhats-members] sshd and mumps process hung
(substitute the actual file name for /tmp/file.txt):
S MYIO=/tmp/file.txt
O MYIO W $T
C MYIO
GTMS MYIO=/home
On Jul 10, 2006, at 4:18 PM, Ismet Kursunoglu wrote:OK - doing this and setting OPEN PARAMETERS:(NEWVERSION:VARIABLE:NOREADONLY) or NEWVERSION works, writing out the file. The point of that test with the explicit OPEN was to see if the file could be opened and modified, and we found that it
On Jul 8, 2006, at 10:03 PM, Nancy Anthracite wrote:
That HFS Device you have there seems like it should work. What
does it have
when you inquire into it? Or did you try changing the $I to /tmp/
hfs.dat?
Do you have the routine VAFCHFS on your system?
Select OPTION: 5 INQUIRE TO
On Jul 8, 2006, at 10:22 PM, Ismet Kursunoglu wrote:When I try to write to a file it just kicks me out; OUTPUT FROM WHAT FILE: NEW PERSON// SORT BY: NAME// START WITH NAME: FIRST// FIRST PRINT FIELD: .01 NAME THEN PRINT FIELD: Heading (S/C): NEW PERSON LIST// testing DEVICE: HFS Host File
Thanks Greg, I did not to that - thanks for the directions.
I am now finally taking all of these valuable lessons and
beginning to organize them - i.e. Kernel, FileMan, error/debugging,
M, etc.. Many of these things have been covered in prior Hardhat
postings - and the core items are in the
Ismet, for what it's worth, my HFS record is a little different from
yours. Here is mine:
NUMBER: 39 NAME: GTM-UNIX-HFS
$I: /tmp/vistahfs.txt ASK DEVICE: YES
ASK PARAMETERS: NO
LOCATION OF TERMINAL: Host File Server (GT.M)
ASK HOST FILE: YES
On 7/9/06, Ismet Kursunoglu [EMAIL PROTECTED] wrote:
...
The other question is - and this is looming pretty large - what I am
going to do about a production system? Should I push on with the FOIA?
I fear the various patches that have to be applied i.e. for example to
maintain a local MPI -
On Jul 9, 2006, at 12:51 AM, Ismet Kursunoglu wrote: I try to annotate the notes with my layman understanding Hardly!- it is helpful to have a log of the whole process. No doubt this will be a lifelong "event" - I guess it should/could even be part of maintaining a VistA system - no doubt there
How did you create the GTM-UNIX-HFS device? Was it part of your DEVICE
file from the initial installation?
On Sun, Jul 09, 2006 at 08:49:20AM -0400, Kevin Toppenberg wrote:
Ismet, for what it's worth, my HFS record is a little different from
yours. Here is mine:
NUMBER: 39
Think differential diagnosis here. Thee are number of reasons why
your HFS device could fail:
1. It may be that the file cannot be opened for reading/writing/
modification (which are you trying to do?)
Both. The thing I don't understand is what where the GTM-UNIX-HFS
device is derived
: Re: [Hardhats-members] sshd and mumps process hung
Think differential diagnosis here. Thee are number of reasons why
your HFS device could fail:
1. It may be that the file cannot be opened for reading/writing/
modification (which are you trying to do?)
Both. The thing I don't understand
I'm sorry, but I don't remember.
Kevin
On 7/9/06, Ismet Kursunoglu [EMAIL PROTECTED] wrote:
How did you create the GTM-UNIX-HFS device? Was it part of your DEVICE
file from the initial installation?
On Sun, Jul 09, 2006 at 08:49:20AM -0400, Kevin Toppenberg wrote:
Ismet, for what it's
Kursunoglu [EMAIL PROTECTED]
To: hardhats-members@lists.sourceforge.net
Sent: Sunday, July 09, 2006 5:02 PM
Subject: Re: [Hardhats-members] sshd and mumps process hung
Think differential diagnosis here. Thee are number of reasons why
your HFS device could fail:
1. It may
PROTECTED];
hardhats-members@lists.sourceforge.net
Sent: Sunday, July 09, 2006 4:40 PM
Subject: Re: [Hardhats-members] sshd and mumps process hung
Thank you. Now I am getting somewhere - now it is complaining about
the device being busy.. I will work on it more and report back this
evening
I tried playing with it:
GTMS MYIO=home/nancy/testIO.txt
GTMO MYIO W $T
%SYSTEM-E-ENO13, Permission denied
GTMS MYIO=/tmp/TestIO.txt
GTMO MYIO W $T
1
GTMC MYIO
GTMH
[EMAIL PROTECTED]:~$ ls /tmp/TestIO.txt
/tmp/TestIO.txt
[EMAIL PROTECTED]:~$ cat /tmp/TestIO.txt
So, what is $T ?
On Sunday
PROTECTED]
To: hardhats-members@lists.sourceforge.net
Sent: Sunday, July 09, 2006 9:26 PM
Subject: Re: [Hardhats-members] sshd and mumps process hung
I tried playing with it:
GTMS MYIO=home/nancy/testIO.txt
GTMO MYIO W $T
%SYSTEM-E-ENO13, Permission denied
GTMS MYIO=/tmp/TestIO.txt
GTMO
On Jul 9, 2006, at 9:26 PM, Nancy Anthracite wrote:I tried playing with it: GTMS MYIO="home/nancy/testIO.txt" GTMO MYIO W $T %SYSTEM-E-ENO13, Permission denied GTMS MYIO="/tmp/TestIO.txt" GTMO MYIO W $T 1 GTMC MYIO GTMH [EMAIL PROTECTED]:~$ ls /tmp/TestIO.txt /tmp/TestIO.txt [EMAIL
Nancy, On Jul 9, 2006, at 11:26 PM, Nancy Anthracite wrote:I tried playing with it:GTMS MYIO="home/nancy/testIO.txt" I'm curious - (if you get time) would it make a difference if you started this file reference with a slash, as in "/home/nancy/testIO.txt"?GTMO MYIO W $T%SYSTEM-E-ENO13, Permission
On Jul 9, 2006, at 9:31 PM, Chris Richardson wrote:Nancy; $T is $TEST, the results of the last IF test, Timeout, Timed Lock Attempt, or the success of the opening of a device. So if you are going to use $TEST, you need to test it immediately after the action you are concerned with. One of the
Well after a few hours today I couldn't get this to work because I
couldn't load the wonderful file you created. For whatever reason I
couldn't get the HFS device to write to the file system (standard ext3
sitting on a RAID 10 system of new SATA disk drives). I did learn more
about the whole w/r
That HFS Device you have there seems like it should work. What does it have
when you inquire into it? Or did you try changing the $I to /tmp/hfs.dat?
On Sunday 09 July 2006 00:37, Ismet Kursunoglu wrote:
Well after a few hours today I couldn't get this to work because I
couldn't load the
On Jul 8, 2006, at 10:03 PM, Nancy Anthracite wrote:That HFS Device you have there seems like it should work. What does it have when you inquire into it? Or did you try changing the $I to /tmp/hfs.dat? Do you have the routine VAFCHFS on your system? Gregory Woodhouse[EMAIL PROTECTED]"Judge a
That HFS Device you have there seems like it should work. What does it have
when you inquire into it? Or did you try changing the $I to /tmp/hfs.dat?
When I try to write to a file it just kicks me out;
OUTPUT FROM WHAT FILE: NEW PERSON//
SORT BY: NAME//
START WITH NAME: FIRST//
FIRST
You should be able to send a mupip interrupt to the hung process and get
it to dump its current state.
I didn't know there was such a command ? You mean like literally
'mupip interrupt'? Excuse my ignorance. I was killing the process with
mupip stop PID
If it is in a tight loop, it should be
From what I've read, the problem is not OPTION specific -- it's more of a
general problem when doing anything within menu manager. If you're hanging
when you issue a ? at a menu prompt something's really messed up --
either corrupted code or a db problem.
I am sorry for the confusion. It
Get the PID of the mumps process and execute the following command at
a linux shell prompt:
strace -pPID
Let us know what you see.
--Marc
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Comments below.
Regards
-- Bhaskar
Ismet Kursunoglu wrote:
You should be able to send a mupip interrupt to the hung process and get
it to dump its current state.
I didn't know there was such a command ? You mean like literally
'mupip interrupt'? Excuse my ignorance. I was killing the
On Fri, Jul 07, 2006 at 10:44:12AM -0400, Dan wrote:
Okay, I created a KIDS build for you that has a routine and option in it.
ftp://ftp.mcenter.com/pub/misc/zzdb.kids
After you install it:
Dan, Thanks very, very much for all of this work. I am tardy with
installing the KIDS
I was at the manager menu and used the system status option and
the session hung with this remaining (this was over an ssh session running
Bhaskar's FOIAVistA20060615 with gtm_V5.1-000)
Select Systems Manager Menu Option: ?
Core Applications ...
Device Management ...
Is this your first time in to this menu?
On Thursday 06 July 2006 14:59, Ismet Kursunoglu wrote:
I was at the manager menu and used the system status option and
the session hung with this remaining (this was over an ssh session running
Bhaskar's FOIAVistA20060615 with gtm_V5.1-000)
Select
I forgot to mention -
~$ uname -a
Linux giant 2.6.8-11-amd64-k8-smp #1 SMP Sun Oct 2 20:03:22 UTC 2005 x86_64
GNU/Linux
[EMAIL PROTECTED]:~/hui/error/cprs$ vmstat
procs ---memory-- ---swap-- -io --system-- cpu
r b swpd free buff cache si sobi
No. I was using it over the last 4-5 days having loaded and configured
this new FOIA release- it was working just fine. I had made two
changes: adding Kevin's routines for the default editor (vim in my
case) as well as the MPI/Austin polling issue. It was running fine
from this menu.
Is this
If you can replicate the problem, I'd recommed signing in through ^ZU
and interrupting the process with kill -2. I don't know if ctrl-C will
even send an interrupt, it might just break the connection.
Look at the option definition and see if there is any code vulnerable
tyo being put into a tight
--- Greg Woodhouse [EMAIL PROTECTED] wrote:
Finally, and this is a long shot, it's just
possible
that a corruption of some sort in ^XUTL has caused a node to point
back
to itself. (Note, BTW, that data in ^XUTL is stored under the user's
DUZ. Did you sign in as the same user each time?)
Ismet --
You should be able to send a mupip interrupt to the hung process and get
it to dump its current state.
If it is in a tight loop, it should be burning CPU cycles, and should
show up under top
By corruption I think Greg means inconsistent data from an application
perspective. If
On Thu, Jul 06, 2006 at 12:58:10PM -0700, Greg Woodhouse wrote:
If you can replicate the problem, I'd recommed signing in through ^ZU
and interrupting the process with kill -2. I don't know if ctrl-C will
Select Systems Manager Menu Option: ?
Core Applications ...
Device
--- Ismet Kursunoglu [EMAIL PROTECTED] wrote:
It is reproducible whenever I enter the Operations Mangement option
follow by
the 'System status' choice.
I appreciate your comments and will get you more information.
Okay, look to see what code is invoked by this option. You can do
--- Ron Fox [EMAIL PROTECTED] wrote:
To rule out a problem with the sshd, try communicating with it using
the
ssh escape sequences (see man ssh for details) over your ssh
session.
If the sshd and your connection to it are alive and healthy, pressing
and
releasing the 3 keys enter~? one
DOES hang, try cleaning your partition like so
K
D ^XUP
It continued to hang and evoking the above it continues to hang.
Ah, but now when I kill the process I see this
Select OPTION NAME: ?
Answer with OPTION NAME, or UPPERCASE MENU TEXT
Do you want the entire 9452-Entry OPTION
--- Ron Fox [EMAIL PROTECTED] wrote:
To rule out a problem with the sshd, try communicating with it using
the
ssh escape sequences (see man ssh for details) over your ssh
session.
If the sshd and your connection to it are alive and healthy, pressing
and
releasing the 3 keys
On Jul 6, 2006, at 4:34 PM, Ismet Kursunoglu wrote:Ah, but now when I kill the process I see this Select OPTION NAME: ? Answer with OPTION NAME, or UPPERCASE MENU TEXT Do you want the entire 9452-Entry OPTION List? n (No) Select OPTION NAME: system 1 SYSTEM AUDIT MENU XUAUDIT MAINT
On Jul 6, 2006, at 4:21 PM, Ismet Kursunoglu wrote:NUMBER: 32 NAME: XUSTATUS MENU TEXT: System Status TYPE: action CREATOR: SCHLEHUBER,CAMERON DISPLAY OPTION?: YES E ACTION PRESENT: YES DESCRIPTION: Uses Operating System utility to show
From what I've read, the problem is not OPTION specific -- it's more of a
general problem when doing anything within menu manager. If you're hanging
when you issue a ? at a menu prompt something's really messed up --
either corrupted code or a db problem.
Open up another session window and
56 matches
Mail list logo
