> Could you please tell me what files will be clear text with classic and 
> binary with berkeleydb?

The files which are plain text do not exist with berkeleydb, as all is recorded 
in some database related files only.

classic:

$ ls -F $SGE_ROOT/default/spool/qmaster
admin_hosts/           calendars/  cqueues/     hostgroups/   jobseqnum  
operators  qinstances/       submit_hosts/  zombies/
advance_reservations/  centry/     exec_hosts/  jobs/         managers   pe/    
    qmaster.pid       users/
arseqnum               ckpt/       heartbeat    job_scripts/  messages   
projects/  resource_quotas/  usersets/

BDB:

$ ls -F $SGE_ROOT/default/spool/qmaster
arseqnum  heartbeat  job_scripts/  jobseqnum  messages  qmaster.pid

$ ls -F $SGE_ROOT/default/spool/spooldb
__db.001  __db.002  __db.003  __db.004  __db.005  __db.006  log.0000002132  sge 
 sge_job


> 
>>> I'll let you know tomorrow how it goes.
> 
> For now it's ok.. sge_qmaster on the frontend and sge_execd on the execute 
> nodes work.
> Now I need to export/import the config from old to the new server.
> 
> 
>>> 
>>> But I'm new to arc and that will be a bit of a challange. :-)
>>> Can I add it later or I need to do it together with SoGE?
>> You mean ARCo for the accounting? As I wrote in the other eMail: we never 
>> used it, as we never had a need for it. There was the idea to use it, but 
>> essentially the pending queue is so short, and there are only short phases 
>> where some waiting time exists, that we skipped this.
> 
> Yes. I mean ARCo for the accounting and I hope it can help understand usage 
> statistics in a better way that acct (/opt/sge/default/common/accounting) 
> does.

The raw information is the same. The accounting file's format is documented on 
`man accounting`.

-- Reuti
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users

Reply via email to