Topic: [Announce] Dar - Disk Archive (alpha build)

[jpl]

... by the timeout you set (value is in seconds, not in hours).

The bigger is the mistake...

Timeout command use timeout value in seconds. Not easy, so I decided my panel should ask for backup timeout in hours... and I have forgotten hours to seconds conversion in my backup script.

All seems more clear now. You got only a few Mb of datas backuped in... one second.

Thank for pointing this problem.

[icpix]

jpl----
I tried 3600 but control panel only wants 1-24...
Need another rpm?
----best wishes, Robert

[icpix]

jpl----
Progress... I am allowed only 1-24 (seconds) in the box so I try 24.
This time my filesize transferred increases from ~1.7MB to 47MB.
ie the max I can now backup in 24secs (approx 144GB/day)
LAN is a gigabit LAN - no other traffic but my workstations.
----best wishes, Robert

[jpl]

jpl----
I tried 3600 but control panel only wants 1-24...
Need another rpm?
----best wishes, Robert

shure...

But before the new rpm you can set it with the command :

/sbin/e-smith/db configuration setprop backupwk Timeout value_in_seconds

[icpix]

jpl----

Code: [Select]

/sbin/e-smith/db configuration setprop backupwk Timeout 3600
but how to tell the control panel not to check for 1-24?
----best wishes, Robert

[byte]

jpl----

Code: [Select]

/sbin/e-smith/db configuration setprop backupwk Timeout 3600
but how to tell the control panel not to check for 1-24?
----best wishes, Robert

You would have to run directly from script...

/etc/e-smith/events/actions/workstation-backup-dar

See the bug post by Darrell.

[jpl]

jpl----

Code: [Select]

/sbin/e-smith/db configuration setprop backupwk Timeout 3600
but how to tell the control panel not to check for 1-24?
----best wishes, Robert

The problem is not in the check or in the panel, which is correct, but in the subsequent treatment which mut convert hours in seconds.

The modification is here (line 1679 of /etc/e-smith/web/functions/backup) :

Code: [Select]

   if  (( $timeout < 1 ) || ( $timeout > 24 ))
    {
        esmith::cgi::genResult(
            $q, $fm->localise('ERR_INVALID_TIMEOUT')
        );
        return;
    }


must become :

Code: [Select]

   if  (( $timeout < 1 ) || ( $timeout > 24 ))
    {
        esmith::cgi::genResult(
            $q, $fm->localise('ERR_INVALID_TIMEOUT')
        );
        return;
    }
    else
    {
        $timeout = ($timeout*3600)-60;
    }


with this modification, it should be ok.

[icpix]

jpl----
I edited that file as you wrote.
Still the control panel checks for 1-24.
Do I have to reboot or something?
----best wishes, Robert

[jpl]

jpl----
I edited that file as you wrote.
Still the control panel checks for 1-24.
Do I have to reboot or something?
----best wishes, Robert

Normal : you give the timeout in hours, but it is now correctly converted in seconds by the script.

You can verify it by typing :

/sbin/e-smith/db configuration getprop backupwk Timeout

[icpix]

jpl----
I have 3600 (seconds) manually entered.
This is not my problem here.
The control panel, on exit, keeps protesting for values 1-24...
When I go back into the control panel I find what I entered is missing.
Yes, I still have 3600 but this isn't the remaining issue.
----best wishes, Robert

[icpix]

jpl----
Oh! I see. Your edit makes it into hours and now I must take out
3600 and put in 1... I'm not a programmer (photographer);~)
----best wishes, Robert

[icpix]

jpl----
Still doesn't work if you go around again in a circle to check.
Now there is a strange number for timeout which itself does
not get accepted after exit (must be 1-24)...
----best wishes, Robert

[icpix]

jpl----
It still doesn't make sense to me.
Yes, I know I am not a programmer but I can do maths.
Your code says:
$timeout = ($timeout*3600)-60;
...that '-' minus symbol... maybe it should be a divide symbol '/'?
Try for 1hrs when I return to the control panel it is 3540 (1x3600)-60.
Try for 2hrs when I return to the control panel it is 7140 (2x3600)-60.
----best wishes, Robert

[icpix]

How do I kill this thing? I've let it do its stuff for over the nominal '1hr' for
which it was configured. It's taking 98% CPU utilisation and there are no
files in the destination share (yet?). The OS drive's space hasn't gone
down by anything significant so just what DAR is doing with 98% of a
pair of 3.4GHz Xeons without producing I do not know. 'htop' shows
PID 14219 for the DAR process... how do I stop DAR?
----best wishes, Robert

[byte]

type...

kill 14219

but be careful when using the kill command. do a man kill for more usage