[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference csc32::consolemanager

Title:	POLYCENTER Console Manager
Notice:	Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS:
Moderator:	CSC32::BUTTERWORTH

Created:	Thu Aug 06 1992
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	1541
Total number of notes:	6564

562.0. "Datafiles. where are they when you don't SAVE" by CSC32::PITT () Tue Jan 17 1995 21:27

    
    
    PCM 1.5 on OSF.
    
    
    
    Customer was in the configuration editor and he was editing one of his
    systems ( changing tty device and port number) , he hit APPLY and OK and
    went to save the new changes but hit USE and return instead of cancel.
    Now his configuration file appears to be empty when he starts up PCM.
    
    Where are the databases kept? We looked just about everywhere under
    /usr/opt/DCR150 and found no datafiles. 
    
    Should hitting 'use' instead of 'save' wipe out the file you were in or
    shouldn't it just save the old copy and not include the changes that
    didn't get saved???
    
    thanks

T.R Title User Personal
Name Date Lines

562.1 OPG::SIMON Wed Jan 18 1995 10:37 41

T.R	Title	User	Personal Name	Date	Lines
562.1		OPG::SIMON		`Wed Jan 18 1995 10:37`	41
	Hi, interesting one this. Let me confirm what happened. In editor made changes and asked to USE but did not specify a file. This wiped out the in memory editor structures and tried to load a non-existant file. Now that is an oversight as we should not wipe out the memory stuff until we have validated the file. Now the customer must have SAVED or EXITed for the empty database to have been written (Quit would have avoided that). So name the Permenant database file /var/opt/console/data/console_cfg.dat is empty. I assume the customer has never done an Export to text as recommended in the User Guide!! Now if the customer has NOT tried to reconfigure or restart PCM since the above tragedy there will be a copy of the database in: /var/opt/console/tmp/console_cfg.dat as we copy it from data to tmp on each startup or reconfigure. If this is the case: # cp /var/opt/console/tmp/console_cfg.dat /var/opt/console/data/console_cfg.dat then restart and he will have the pre edit data. If not then Oh dear he is back to scratch. First he must get the base template database installed # console -E import /usr/opt/DCR150/templates/console_config.PORT Then go into editor and key in his database. Finally export it to a text file against such an occurence. Cheers Simon...

Hi,
   interesting one this. Let me confirm what happened.

In editor made changes and asked to USE but did not specify a file.

This wiped out the in memory editor structures and tried to load a non-existant
file. Now that is an oversight as we should not wipe out the memory stuff until
we have validated the file.

Now the customer must have SAVED or EXITed for the empty database to have been 
written (Quit would have avoided that).

So name the Permenant database file /var/opt/console/data/console_cfg.dat is
empty.

I assume the customer has never done an Export to text as recommended in the 
User Guide!!

Now if the customer has NOT tried to reconfigure or restart PCM since the above
tragedy there will be a copy of the database in:    				
					/var/opt/console/tmp/console_cfg.dat
as we copy it from data to tmp on each startup or reconfigure. If this is the
case:

# cp /var/opt/console/tmp/console_cfg.dat /var/opt/console/data/console_cfg.dat

then restart and he will have the pre edit data.

If not then Oh dear he is back to scratch.

First he must get the base template database installed

# console -E import  /usr/opt/DCR150/templates/console_config.PORT

Then go into editor and key in his database.

Finally export it to a text file against such an occurence.

Cheers Simon...