bobs-devel — Developer mailing list

[Bobs-devel] feature enhancements and some design issues

[Rene R. <re...@gr...>]

Project based backup proposal.

Definition of a project:

- each root directory in a share is a project.

Needed changes:

- To restore a project we need to be able to select an entire project 
easily.

- Full backups. Project files are treated as one file. Incremental 
backups must make an increment of the entire project every time. This 
will take up a lot more space on the disk. Only keeping one copy of 
files that have not changed would be a good idea. This requires a way of 
  checking this. A simple "compare" or an MD5 checksum. This will 
require a way of tracking these files and what backups they belong to. 
Either using a database or a seperate index of these files.

- The ability to manually start a backup from bobs would be a good idea.


Design Issues:

I was originally thinking of backup methods as a sort of plugins to 
bobs. Bobs would be the controller and the plugins would handle the 
actual code in respect to making backup and restoring files.
This still seems to be the way to do it.

I think some of the functions in class_backup and class_restore should 
be extracted to something like backup_smb.php, backup_nfs.php and 
restore_nfs.php.
A clean and well defined data structure should be used to pass data to 
the plugins.

This would make it easier to make stuff like "backup_smb_project.php"

Rene

[Bobs-devel] filename problems

[Rene R. <re...@gr...>]

I've been looking into the filename problems.

It seems to me that escaping filenames in PHP will ony lead to a 
constant headache (which is not what I need right now ;)

I've found a few Bash tricks that look really promising but I haven't 
cracked the problem yet. I'm able to make Bash escape a filename with 
weird characters in it. But I'm still not able to do it with input from 
a list.
When (if?) I get this working we should be able to stop worrying about 
filenames.
If you know any Bash experts please ask if they can help.

-Rene

Re: [Bobs-devel] work to be done

[Rene R. <re...@gr...>]

So far, so good..

I've got smb backup and restore working.
Still need to do nfs backup (should be a walk in the park)

Server ini file changes include:
"smb_share" The name of the remote smb share
"backup_method" The method used for making backup. (rsync/smb/nfs)
"restore_method" Method used for restoring files (smb/nfs)
"server_ip" is optional. If used I assume its a static IP.
"share" is now used as a descriptive label for the backup. (eg. 
/backupdir/bobsdata/server/share)
"rsync_share" is the name of the remote rsync share
"password" is now cleartext.

I found what seems to be a bug in filename handling when restoring 
files. I still haven't isolated the precise cause.
The admin interface is broken in regards to creating correct ini files.


Some things to think about:
I've got a share which contains several projects. These files are all 
"linked" together on a project basis. Making backups of individual files 
does not make that much sense since they depend on each other. I was 
thinking something in the line of making a manual "do backup now" button.
Maybe creating a list of the projects and being able to select one (or 
more) of them for a backup.
A set of rules for the list could be an option. eg. each dir in the root 
of the share is a project. Only make full backup of each project.

Any good ideas?

An editor for the exclude lists and the linked files list is needed.
Maybe someone has already made one we can use.

I'll post news as I go along. I'll do a cvs commit of the changes soon.

-Rene




Rene Rask wrote:
> 
> I think the settings system will have to be reimplemented.
> I need some additional settings and options.
> Cleartext passwords are needed for smb access.
> Security must be enabled using .htaccess files to prevent password from 
> being read.
> Files must be chmodded to 0600 to prevent shell users from reading the 
> files.
> 
> I'll begin working on the SMB access method.
> Also an nfs only method would be nice. Rsync is not strictly nessecary 
> to make backups. But it is a nicer way of doing it since it will (I 
> think) use less processor power and consume less bandwidth.
> 
> Basically this can be split into two tasks. A new configuration editing 
> system and a new backup class. (I think I'll rename function.php to 
> class_backup.php)
> A more generic configuration editor would be nice.
> If you want to help break things please let me know. I'll not commit my 
> work to cvs until it works to avoid breaking the cvs tree.
> 
> Please comment on these ideas.
> 
> I've tried to descripe how I think the new settings should be created.
> 
> When clicking on "create new server" the following questions are asked
> - choose backup method:        Smb / Nfs / Rsync
> - choose restore method:    Smb / Nfs
> - choose network address type:    Dns / static Ip
> 
> Based on the above answer the appropriate settings below are shown.
> - Login name:        Login name for this server (the login needed for 
> eg. smb access)
> - Password:        Password (stored as clear text. Needed for smb access.)
> - Server name:        The servers network name
> - Server IP address:    The servers Static IP address
> - Rsync share name:    Rsync share name
> - NFS share path:    NFS share path
> - NFS share name:    Descriptive name for the share (unique name for 
> this server)
> - SMB share name:    SMB share name
> - Active:        Is this server active (do I need to make backups?)
> - Backup days:        Which weekdays to make backups.
> 
>     -- options not implemented yet --
> - Incrementals:        How many incremental backups should there be.
> - Compress:        Should incremental files be compressed?
> 
> 
> 
> -Rene
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Caffeinated soap. No kidding.
> http://thinkgeek.com/sf
> _______________________________________________
> Bobs-devel mailing list
> Bob...@li...
> https://lists.sourceforge.net/lists/listinfo/bobs-devel

[Bobs-devel] work to be done

[Rene R. <re...@gr...>]

I think the settings system will have to be reimplemented.
I need some additional settings and options.
Cleartext passwords are needed for smb access.
Security must be enabled using .htaccess files to prevent password from 
being read.
Files must be chmodded to 0600 to prevent shell users from reading the 
files.

I'll begin working on the SMB access method.
Also an nfs only method would be nice. Rsync is not strictly nessecary 
to make backups. But it is a nicer way of doing it since it will (I 
think) use less processor power and consume less bandwidth.

Basically this can be split into two tasks. A new configuration editing 
system and a new backup class. (I think I'll rename function.php to 
class_backup.php)
A more generic configuration editor would be nice.
If you want to help break things please let me know. I'll not commit my 
work to cvs until it works to avoid breaking the cvs tree.

Please comment on these ideas.

I've tried to descripe how I think the new settings should be created.

When clicking on "create new server" the following questions are asked
- choose backup method:		Smb / Nfs / Rsync
- choose restore method:	Smb / Nfs
- choose network address type:	Dns / static Ip

Based on the above answer the appropriate settings below are shown.
- Login name:		Login name for this server (the login needed for eg. smb access)
- Password:		Password (stored as clear text. Needed for smb access.)
- Server name:		The servers network name
- Server IP address:	The servers Static IP address
- Rsync share name:	Rsync share name
- NFS share path:	NFS share path
- NFS share name:	Descriptive name for the share (unique name for this server)
- SMB share name:	SMB share name
- Active:		Is this server active (do I need to make backups?)
- Backup days:		Which weekdays to make backups.

	-- options not implemented yet --
- Incrementals:		How many incremental backups should there be.
- Compress:		Should incremental files be compressed?



-Rene

[Bobs-devel] make install is working for me

[Joe z. <jz...@at...>]

I think I've got the ./configure and 'make install' working pretty good. 
I'm changing permissions and ownership only on the files and directories 
that need it. Everything else will be owned by root, assuming you run 
'make install' as root.

I plan to create a 'make install_cron'.

I don't know if I've already said this, I'm very impressed with the way 
you use frames, and with the directory tree written in php, and I think 
the menu tabs look very professional. You do good work.

I don't plan to get much more done on bobs this week because I'm 
preparing for next week's vacation.

Re: [Bobs-devel] siteroot and include files

[Rene R. <re...@gr...>]

On Sat, 2002-06-22 at 07:00, Joe zacky wrote:
> Rene,
> 
> There's a problem with $siteroot if I put the bobs web pages in my 
> /home/joe/public_html directory and access it as 
> http://jupiter.zebra.com/~joe/bobs/admin.php. $siteroot evaluates to 
> "/var/www/html/~joe/bobs", when it needs to be 
> "/home/joe/public_html/bobs" for the includes in admin.php to work 
> right. There's some url conversion going on because of the "UserDir 
> public_html" directive in httpd.conf. If I change the includes from:
> 
>     require($siteroot . "/inc/config.php");
> to
>     require("inc/config.php");

I guess there are two options here. Either we go with a relative path 
or a "realpath" command. PHP has a command like that but I'm not sure
it'll do the trick.

The code is really not consistent on this. Some parts use relative paths
and others use the full path.
I've mostly used full paths and prefer that, since it gives me a warm
fuzzy feeling of being in control. 

But if it posses to many problems we should go with the relative paths.

-Rene


> then it works. As long as the "inc" files are relative to the specified 
> path, it should be okay. I'd like your opinion on that - whenever - 
> there's no rush.
> 
> Joe
> 
> 
> 
> -------------------------------------------------------
> Sponsored by:
> ThinkGeek at http://www.ThinkGeek.com/
> _______________________________________________
> Bobs-devel mailing list
> Bob...@li...
> https://lists.sourceforge.net/lists/listinfo/bobs-devel

Re: [Bobs-devel] CVS question

[Rene R. <re...@gr...>]

On Sat, 2002-06-22 at 06:29, Joe zacky wrote:
> Rene,
> 
> How do you remove the latest revision of a file from the CVS, and do I 
> have the authority to do that? There were a few times when I wanted to 
> pull out some bad changes I made.
> 

I wish I knew. I'd check the cvs man page.
Please let me know if you figure it out.

Rene


> 
> 
> 
> -------------------------------------------------------
> Sponsored by:
> ThinkGeek at http://www.ThinkGeek.com/
> _______________________________________________
> Bobs-devel mailing list
> Bob...@li...
> https://lists.sourceforge.net/lists/listinfo/bobs-devel

Re: [Bobs-devel] todo

[Rene R. <re...@gr...>]

On Sat, 2002-06-22 at 06:03, Joe zacky wrote:
> Rene,
> 
> I saw your additions to the TODO list. I'm getting ready to work on bobs 
> tonight and I have my own "todo" list that I want to run by you.
> 
> 1.    I wasn't clear when I said my makefile "creates the backup data 
> directories". It only creates the main directory and the process... 
> directories, like this:
> 
> <whatever>/bobsdata/
> `-- process
>     |-- cmd
>     |-- mounts
>     `-- session
> 
> It's my understanding the backup directories (current, incoming, and 
> incremental) will be created under "bobsdata", according to config.php. 
> These will be created by the httpd process. So in the makefile I need to 
> find out who the  httpd user is and create the "bobsdata" directory with 
> that user as the owner. I hardcoded the directory name "bobsdata" to 
> ensure that "make install" and "make uninstall" won't damage other data. 
> So "<whatever>/bobsdata" will be the top of the data directory tree.

That sounds good.

> 
> 2.    As far as autoconf and automake, the user shouldn't need to run 
> those after I put "configure" in the CVS. They are only for us 
> developers. autoconf reads configure.in and creates configure. automake 
> reads Makefile.am and creates Makefile.in. ./configure reads 
> Makefile.in, inc/config.php.in and cron/backup.php.in and creates 
> Makefile, inc/config.php and cron/backup.php, and does some other 
> processing too.
> 
> I'm going to put more comments in those files for all our benefit. This 
> is the first time I've really used autoconf and automake, so it's a 
> learning experience, and it's fun!

I still need to read up on those.

> 
> 3.    I introduced a bug in config.php. A comment is added by 
> ./configure as the first line and messes up the session header or 
> something. That'll be fixed.

I've fixed that already.

> 4.    I have some more work to do on the makefile, and I think I'll add 
> a couple items to the TODO list.
> 
> You're replies to my last two emails were very helpful. Some of that's 
> on my todo list, and some I'll put on the main TODO list.
> 
> Take it easy,
> Joe
> 
> 
> 
> -------------------------------------------------------
> Sponsored by:
> ThinkGeek at http://www.ThinkGeek.com/
> _______________________________________________
> Bobs-devel mailing list
> Bob...@li...
> https://lists.sourceforge.net/lists/listinfo/bobs-devel

[Bobs-devel] siteroot and include files

[Joe z. <jz...@at...>]

Rene,

There's a problem with $siteroot if I put the bobs web pages in my 
/home/joe/public_html directory and access it as 
http://jupiter.zebra.com/~joe/bobs/admin.php. $siteroot evaluates to 
"/var/www/html/~joe/bobs", when it needs to be 
"/home/joe/public_html/bobs" for the includes in admin.php to work 
right. There's some url conversion going on because of the "UserDir 
public_html" directive in httpd.conf. If I change the includes from:

    require($siteroot . "/inc/config.php");
to
    require("inc/config.php");

then it works. As long as the "inc" files are relative to the specified 
path, it should be okay. I'd like your opinion on that - whenever - 
there's no rush.

Joe

[Bobs-devel] CVS question

[Joe z. <jz...@at...>]

Rene,

How do you remove the latest revision of a file from the CVS, and do I 
have the authority to do that? There were a few times when I wanted to 
pull out some bad changes I made.

Joe

[Bobs-devel] todo

[Joe z. <jz...@at...>]

Rene,

I saw your additions to the TODO list. I'm getting ready to work on bobs 
tonight and I have my own "todo" list that I want to run by you.

1.    I wasn't clear when I said my makefile "creates the backup data 
directories". It only creates the main directory and the process... 
directories, like this:

<whatever>/bobsdata/
`-- process
    |-- cmd
    |-- mounts
    `-- session

It's my understanding the backup directories (current, incoming, and 
incremental) will be created under "bobsdata", according to config.php. 
These will be created by the httpd process. So in the makefile I need to 
find out who the  httpd user is and create the "bobsdata" directory with 
that user as the owner. I hardcoded the directory name "bobsdata" to 
ensure that "make install" and "make uninstall" won't damage other data. 
So "<whatever>/bobsdata" will be the top of the data directory tree.

2.    As far as autoconf and automake, the user shouldn't need to run 
those after I put "configure" in the CVS. They are only for us 
developers. autoconf reads configure.in and creates configure. automake 
reads Makefile.am and creates Makefile.in. ./configure reads 
Makefile.in, inc/config.php.in and cron/backup.php.in and creates 
Makefile, inc/config.php and cron/backup.php, and does some other 
processing too.

I'm going to put more comments in those files for all our benefit. This 
is the first time I've really used autoconf and automake, so it's a 
learning experience, and it's fun!

3.    I introduced a bug in config.php. A comment is added by 
./configure as the first line and messes up the session header or 
something. That'll be fixed.

4.    I have some more work to do on the makefile, and I think I'll add 
a couple items to the TODO list.

You're replies to my last two emails were very helpful. Some of that's 
on my todo list, and some I'll put on the main TODO list.

Take it easy,
Joe

Re: [Bobs-devel] my "first time" install notes

[Rene R. <re...@gr...>]

On Mon, 2002-06-10 at 08:28, Joe Zacky wrote:
> I put in many hours on 'bobs' this weekend. I learned much about cvs. 
> I'm learning about using autoconf and automake to generate a Makefile.
> 
> If you start in the root of the bobs directory tree, you can build a 
> Makefile with the following commands. It doesn't actually make anything 
> yet, but it does check for some programs and paths and sets variables in 
> the Makefile that I will use during the install.
>     autoconf
>     automake
>     ./configure
> 
> ===================================================
> Some problems I had while installing and using BOBS the first time
> ===================================================
> Problem #1: Got this error on confirm save setting of new server:
> 
> Warning:
> fopen("/var/www/html/joe/bobs/bobscustom/inc/servers/uranus.local.ini","w") 
> - Permission denied in 
> /var/www/html/joe/bobs/bobscustom/inc/class_config.php on line 204
> 
> Fix: INSTALL needs to be sure directory is writeable by web process.

This should really output a warning instead. And a brief description on
how to fix it.


> 
> -----------------
> Problem #2: other shares disappear from admin.php
> 
> After creating a 2nd share in admin.php, the first one no longer shows 
> in the drop-down list.
> 
> Fix: Exit session and login again.

True. My session handling is not at its best. This is a problem in other
places as well.
Just try to do a refresh/reload screen on when logged in as a user.
A todo list item I guess.


> -----------------
> Problem #3: restore from web browser gets error in cmdloop:
>     "mount: only root can do that"
> 
> Fix:    Oh, cmdloop (or check_loop cron job) must be run by root.
> -----------------
> Bug #4: What is this all about! It shows after selecting to restore:
> 
> In inc/class_restore.php
>     Error:  Unable to proceed
>     Error: Not enough free diskspace on remote server. Please free some 
> and try again.
>     Error: 1000 MB plus the size of the files you wish to restore is 
> needed    
> 
> It's only a 1 gig harddrive!
> 
> Fix:    changed to require only 100 MB free space, plus restore files size.

This should be moved to the configuration files. Its there to prevent
bobs from taking all available diskspace. Other applications might fail
and work could be lost in that case. So my reasoning was to make sure at
least X Mb was free.
It's hardcoded for now but should be trivial to move.


> -----------------
> =======================
> Some suggested enhancements
> =======================
> Fixup admin.php "create server details screen". Include more explanation 
> of what each field is.
> I noted the questions I had the first time I saw the screen to the right 
> of the "<-"
> 
> "Should I create backups from this server" <- this activates the 
> selected backup?

This is the main on/off switch for each server. 

> 
> "Users login name" and "Users password" <- creating them now, or 
> existing unix pwd?

For now only one user per share. This is stored in the config.ini files.
I would like some other ways to do this, like local unix users, ldap and
stuff like that.

> 
> "The servers network name" <- short name "uranus", or long 
> "uranus.zebra.com"?
>     Answer: either works.
> 
> "The path the the nfs share is mounted under" <- too many "the"s.
>         <- misleading, this is actually the remote path, not the local 
> mount path.
> 
> "The name of the smb share" <- what smb share? for future use?

For future use. Not active at the moment.

> 
> "Compress incremental files?" <- advantages/disadvantages? What's 
> recommended?
For future use. Not active at the moment.

> 
> "Which days to backup. ( 0 = monday, 1 = tuesday .. etc)" <- format: 123 
> or 1,2,3?
>     Answer: 123
> 
> "Press the Change button to change the settings",
> "Press the Save button save the settings" <- What's difference between 
> "change" and "save"?
>     Remove "change", only need "save"?

"Change settings" applies the settings you've changed.
"save" saves the settings as the were the last time you applied them.
This was intended to have a "reset to last saved" button. I didn't get
around to implementing that. 
It should be nicer.

> -----------------
> Show session name at top of each screen. Sometimes it shows (in dir 
> trees), but not always.
> -----------------
> In history frame, don't keep clock up-to-date, the refreshes are 
> annoying- they make my screen blink, or refresh once per minute.

The reason I update is not the clock but the cmdloop output. You can't
really work unless the cmdloop is free.
The clock is just there to make it easy to see if the refresh is
working.
The history also shows the status of any searches you do. When they were
started and when they are finished.

> -----------------
> Automate most of the INSTALL instructions. (I'm working on that)
> -----------------
> Admin.php option to delete a server configuration.
> -----------------
> When selecting "Browse Restore" and nothing has been selected to restore,
> change message from "The following has occured: Dir tree was not found"
> to something more explanatory.
> Other tab messages should be changed too when there is nothing to display.

I agree. These were messages I put in as I was debugging and developing.
Not messages suitable for end users.

> -----------------
> 

I hope I can get back to work soon, but it'll proably be a week or so
before my head clears.

Rene

Re: [Bobs-devel] CVS Update

[Rene R. <re...@gr...>]

Hi Joe

Just a few comments on these changes

On Sat, 2002-06-15 at 09:29, Joe Zacky wrote:
> I just updated the CVS with a dozen files for use with './configure' and 
> 'make'.
> 
> What it does...
>     checks that you have installed httpd, php, portmap and rsync (gives 
> warnings if you don't).
>     puts the web docs in the web directory.
>     creates the backup data directories.

Directories should be created automatically when running bobs. The only
thing make should do is check that the httpd owner has sufficient access
to do this.

> 
> What it doesn't do (yet)...
>     correct permissions for the httpd process to write to the files.
>     copy the miscellaneous files.
>     perform tests of nfs mount, rsync and cmdloop.
Tests of nfs, rsync should be a part of the admin interface. I would be
logical to have it there, since you would proably like to test a server
when you have created it. 
Make cannot check these things in a proper way.

> 
> Read INSTALL section 7.0 to see how to use it. For now, run 'autoconf' 
> and 'automake' before './configure'.

I guess I'll have to read up on automake and autoconf.
I'll do that as my head gets better ;)

Keep up the good work.

-Rene

[Bobs-devel] CVS Update

[Joe Z. <jz...@at...>]

I just updated the CVS with a dozen files for use with './configure' and 
'make'.

What it does...
    checks that you have installed httpd, php, portmap and rsync (gives 
warnings if you don't).
    puts the web docs in the web directory.
    creates the backup data directories.

What it doesn't do (yet)...
    correct permissions for the httpd process to write to the files.
    copy the miscellaneous files.
    perform tests of nfs mount, rsync and cmdloop.

Read INSTALL section 7.0 to see how to use it. For now, run 'autoconf' 
and 'automake' before './configure'.

Joe Zacky

[Bobs-devel] my "first time" install notes

[Joe Z. <jz...@at...>]

I put in many hours on 'bobs' this weekend. I learned much about cvs. 
I'm learning about using autoconf and automake to generate a Makefile.

If you start in the root of the bobs directory tree, you can build a 
Makefile with the following commands. It doesn't actually make anything 
yet, but it does check for some programs and paths and sets variables in 
the Makefile that I will use during the install.
    autoconf
    automake
    ./configure

===================================================
Some problems I had while installing and using BOBS the first time
===================================================
Problem #1: Got this error on confirm save setting of new server:

Warning:
fopen("/var/www/html/joe/bobs/bobscustom/inc/servers/uranus.local.ini","w") 
- Permission denied in 
/var/www/html/joe/bobs/bobscustom/inc/class_config.php on line 204

Fix: INSTALL needs to be sure directory is writeable by web process.

-----------------
Problem #2: other shares disappear from admin.php

After creating a 2nd share in admin.php, the first one no longer shows 
in the drop-down list.

Fix: Exit session and login again.
-----------------
Problem #3: restore from web browser gets error in cmdloop:
    "mount: only root can do that"

Fix:    Oh, cmdloop (or check_loop cron job) must be run by root.
-----------------
Bug #4: What is this all about! It shows after selecting to restore:

In inc/class_restore.php
    Error:  Unable to proceed
    Error: Not enough free diskspace on remote server. Please free some 
and try again.
    Error: 1000 MB plus the size of the files you wish to restore is 
needed    

It's only a 1 gig harddrive!

Fix:    changed to require only 100 MB free space, plus restore files size.
-----------------
=======================
Some suggested enhancements
=======================
Fixup admin.php "create server details screen". Include more explanation 
of what each field is.
I noted the questions I had the first time I saw the screen to the right 
of the "<-"

"Should I create backups from this server" <- this activates the 
selected backup?

"Users login name" and "Users password" <- creating them now, or 
existing unix pwd?

"The servers network name" <- short name "uranus", or long 
"uranus.zebra.com"?
    Answer: either works.

"The path the the nfs share is mounted under" <- too many "the"s.
        <- misleading, this is actually the remote path, not the local 
mount path.

"The name of the smb share" <- what smb share? for future use?

"Compress incremental files?" <- advantages/disadvantages? What's 
recommended?

"Which days to backup. ( 0 = monday, 1 = tuesday .. etc)" <- format: 123 
or 1,2,3?
    Answer: 123

"Press the Change button to change the settings",
"Press the Save button save the settings" <- What's difference between 
"change" and "save"?
    Remove "change", only need "save"?
-----------------
Show session name at top of each screen. Sometimes it shows (in dir 
trees), but not always.
-----------------
In history frame, don't keep clock up-to-date, the refreshes are 
annoying- they make my screen blink, or refresh once per minute.
-----------------
Automate most of the INSTALL instructions. (I'm working on that)
-----------------
Admin.php option to delete a server configuration.
-----------------
When selecting "Browse Restore" and nothing has been selected to restore,
change message from "The following has occured: Dir tree was not found"
to something more explanatory.
Other tab messages should be changed too when there is nothing to display.
-----------------

[Bobs-devel] got it working!

[Joe Z. <jz...@at...>]

Rene,

I don't know if you'll be able to check your email while in Spain, but 
at least you'll see this when you get back. I finally got it working 
through configuration, backup and restore. It was a struggle. Careful 
reading of your install instructions was a great help.

I made many notes on bugs, suggestions and things to do in the install 
script. I'd like to automate as much of the setup as possible. I think 
an automated install would remove many of the problems I had.

I made small changes to five files so far. I'll document all the above 
mentioned things in another email and get started on the install. I'm 
planning to use a Makefile with options for  make config, make defaults, 
make, make test, make install and make uninstall. That should be 
interesting.

I really like the way you've designed the GUI. I normally don't like 
frames, but you've done a wonderful job of making them functional. I 
especially love the menu tabs.

Joe

[Bobs-devel] patch for admin.php

[Joe Z. <jz...@at...>]

Rene,

I've been going crazy trying to figure out why the admin.php page would 
not display.  It turns out the parse_ini_file() failed because 
"$this->serverdir . $server" evaluated to 
/var/www/html/joe/bobs/bobscustom/inc/servers/CVS/, which is a 
directory. I deleted the CVS directory and the page finally shows. Now I 
can continue with configuration.

$this->servers[$i] = parse_ini_file($this->serverdir . $server);

I patched it with:

if ( filetype($this->serverdir . $server) == "file") {
                        $this->servers[$i] = 
parse_ini_file($this->serverdir . $server);
                        $i++;
                }

P.S. I didn't know php had class functions. It looks like c++. cool...

Joe

[Bobs-devel] Just a notice

[Rene R. <re...@gr...>]

I'm off to Spain, so please don't expect any answers from me until
sometime next week.

I hope you got it working Joe.
If you do you might wanna check the source and please beware that
comments are not always true. Things have changed a lot and some of the
comments are old.

Feel free to commit to cvs.=20

Best regards
Ren=E9

Re: [Bobs-devel] rsync and nfs

[Rene R. <re...@gr...>]

Cool Joe

I've completely forgotten to mention the excludes and how it works

In the inc/excludes/ dir there is a file called "default.excludelist".
This file contains the names of the files and dirs excluded from rsync
backup. Take a look a the rsync documentation to see the precise format
of this file.

BOBS in its current state checks for a file called
<servername>.<sharename> in that dir. If it is not found it will use the
"default.excludelist" file.
To backup ALL files with no exclusions you should create an empty file
called <servername>.<sharename>.
Consider that users will restore files and then BOBS will make backup of
those files again. Currently a dir called "restore_files" is created on
the users share, and restored files are placed in it.
Default settings excludes that dir from the backup process.


I'll add this and your documentation to the cvs.

-Rene



On Tue, 2002-06-04 at 08:30, Joe Zacky wrote:
> Rene,
> 
> rsync and nfs are working now. Here's my notes on what I learned. You 
> may want to add some of it to the INSTALL doc. Tomorrow I'll work on the 
> rest of the config.
> 
> rsync
>         on machine to be backed up, enable rsync
>         ntsysv, then enable rsync (or use chkconfig)
>         /etc/init.d/xinetd restart
> 
> nfs
>         on machine to be backed up:
>         nfs needs to be enabled in kernel or as a module.
>         need to start portmap and nfs (or enable in ntsysv or chkconfig).
>         /etc/init.d/portmap start
>         /etc/init.d/nfs start
> 
>         on 'mount'ing machine
>         nfs needs to be enabled in kernel or as a module.
>         start portmap (or enable in ntsysv or chkconfig).
>         /etc/init.d/portmap start
> 
> Joe
> 
> 
> _______________________________________________________________
> 
> Don't miss the 2002 Sprint PCS Application Developer's Conference
> August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
> 
> _______________________________________________
> Bobs-devel mailing list
> Bob...@li...
> https://lists.sourceforge.net/lists/listinfo/bobs-devel

[Bobs-devel] rsync and nfs

[Joe Z. <jz...@at...>]

Rene,

rsync and nfs are working now. Here's my notes on what I learned. You 
may want to add some of it to the INSTALL doc. Tomorrow I'll work on the 
rest of the config.

rsync
        on machine to be backed up, enable rsync
        ntsysv, then enable rsync (or use chkconfig)
        /etc/init.d/xinetd restart

nfs
        on machine to be backed up:
        nfs needs to be enabled in kernel or as a module.
        need to start portmap and nfs (or enable in ntsysv or chkconfig).
        /etc/init.d/portmap start
        /etc/init.d/nfs start

        on 'mount'ing machine
        nfs needs to be enabled in kernel or as a module.
        start portmap (or enable in ntsysv or chkconfig).
        /etc/init.d/portmap start

Joe

Re: [Bobs-devel] New release

[Rene R. <re...@gr...>]

Yes I did see your get the bobs-devel mail. I just forgot to change to
reply-to.

I just got rid of the mysql dependency using a rather ugly "sed" command
instead. I wish I was better a make RE's ... It takes me hours every
time I need to make one.
I haven't tested this a lot. But I can't see any situations were it
would fail.

-Rene



On Tue, 2002-06-04 at 05:34, Joe Zacky wrote:
> Did you see my emails to the bobs-devel mailing list? It took me a while=20
> to figure out SourceForge cvs.
>=20
> I'm sitting down right now to finish setting up rsync, nfs, and the=20
> configuration. Then the fun begins.
>=20
> Joe
>=20
> Rene Rask wrote:
>=20
> >Did you get it up and running?
> >
> >I'm really looking forward to some input on the user aspect of it.
> >
> >-Rene
> >
> >On Tue, 2002-06-04 at 03:11, Joe Zacky wrote:
> > =20
> >
> >>Good move. I think the README and INSTALL updates are worth it.
> >>
> >>Rene Rask wrote:
> >>
> >>   =20
> >>
> >>>Hi=20
> >>>
> >>>I decided to jump the gun and do a quick release. Based on the lack of
> >>>documentation in the previous release.
> >>>
> >>>That will make users without cvs able to use the latest and greatest ;=
)
> >>>
> >>>
> >>>Best regards
> >>>Ren=E9
> >>>
> >>>
> >>>_______________________________________________________________
> >>>
> >>>Don't miss the 2002 Sprint PCS Application Developer's Conference
> >>>August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
> >>>
> >>>_______________________________________________
> >>>Bobs-devel mailing list
> >>>Bob...@li...
> >>>https://lists.sourceforge.net/lists/listinfo/bobs-devel
> >>>
> >>>=20
> >>>
> >>>     =20
> >>>
> >>   =20
> >>
> >
> >
> >
> > =20
> >
>=20

[Bobs-devel] compiling...

[Joe Z. <jz...@at...>]

Rene,

rsync is working for me. I'm working on nfs now. I didn't have it 
compiled into my kernel or modules. Got that done on the machine to be 
backed up, now I have to compile in nfs on my desktop. I think that's as 
far as I'll get tonight.

Joe

[Bobs-devel] A list of things to do

[Rene R. <re...@gr...>]

Here is a quick overview of what I think needs to be done
Not listed in any kind of order.

1. Filename testing. Filenames are mostly a problem when restoring. This
will need some more testing. I'm running this on 4 servers with mac,
linux and windows users so it has been real world tested, but I would
like to make a test suite of files with "funny" names.

2. Use something else than the "replace" command (used in function.php)

3. Make a unified format for file listings. Currently two are in use.
Some functionality depends on the differences between the two. A unified
format would take up a little more space, but be much more useful when
extending bobs with more features.

4. User management. Something needs to be done here. I would appreciate
feedback on how you would like users to be managed.

5. A user help guide to replace the todo.php that is currently displayed
when pressing help.

6. Language support. This would be something like a html rendering class
with support for languages.=20

7. File sequence detection and handling. This would probably be
integrated with the unified list format.

and much more..=20

Please pitch in if you have anything to add to the list.

I'll put this in a TODO file at some point


-Ren=E9

[Bobs-devel] New release

[Rene R. <re...@gr...>]

Hi=20

I decided to jump the gun and do a quick release. Based on the lack of
documentation in the previous release.

That will make users without cvs able to use the latest and greatest ;)


Best regards
Ren=E9

[Bobs-devel] cvs checkout working

[Joe Z. <jz...@at...>]

Rene,

I got the cvs checkout working. I had to actually read the cvs 
instructions! They say to login once to create your home directory:
    ssh -l jzacky cvs.sourceforge.net

I wrote a shell function to checkout from cvs:

cobobs() {
        cd /var/www/html/joe/bobs;
        export CVS_RSH=ssh;
        export CVS...@cv...:/cvsroot/bobs;
        cvs co bobs;
        }
export -f cobobs

So I only have to type "cobobs".

I'll see what happens when I try to checkin - I hope I don't crash the 
whole directory! You have a local backup, right?

Joe