RFE - FreeBSD Port: zfs-snapshot-mgmt-20090201_2

2012-06-28 Thread Karli Sjöberg
Hi!

I am a storage-technician working at the Swedish University of Agriculture and 
we are using zfs-snapshot-mgmt to create scheduled snapshots, but are failing 
on our disaster-recovery machine because of:

/usr/local/bin/zfs-snapshot-mgmt:130:in `join': can't convert nil into String 
(TypeError)
from /usr/local/bin/zfs-snapshot-mgmt:130:in `snapshots'
from /usr/local/bin/zfs-snapshot-mgmt:137:in `snapshots_to_remove'
from /usr/local/bin/zfs-snapshot-mgmt:145:in `remove_snapshots'
from /usr/local/bin/zfs-snapshot-mgmt:213
from /usr/local/bin/zfs-snapshot-mgmt:210:in `each'
from /usr/local/bin/zfs-snapshot-mgmt:210

Now, since this is a disaster-recovery unit, I would rather not have to have 
all filesystems mounted for the script to function as we have many servers with 
many file systems backing up towards this unit, which would result in quite 
alot of mounts that are completely unnecessary to the backup server itself. I 
also consider it a potential security risk having all these file systems, from 
all of these different machines mounted in the same place(server). I mean, if 
someone would like to steal as much valuable data as possible, why crack 
hundreds of servers and steal it piece by piece when you could just crack one 
and have it all, right? That doesn´t really make sense because if someone were 
to crack the backup server they could just mount all filesystems themselves, 
but only if they knew they were there. But also having them mounted feels like 
just handing it to them.

Unfortunately I know nothing about programming so I can´t be of any help, 
besides testing patches, but do you think this can be done? Change the script 
so that it doesn´t require the file systems to be mounted for it to be able to 
take snapshots?


Med Vänliga Hälsningar
---
Karli Sjöberg
Swedish University of Agricultural Sciences
Box 7079 (Visiting Address Kronåsvägen 8)
S-750 07 Uppsala, Sweden
Phone:  +46-(0)18-67 15 66
karli.sjob...@slu.semailto:karli.sjob...@adm.slu.se

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: [HEADS UP] Ports tree migration to Subversion

2012-06-28 Thread mbsd
Hi list.

It will be wonderful. When src had moved to svn, nobody cared about make
update command.
I wish to had this in ports makefile:

--- /usr/ports/Makefile 2012-06-07 09:26:08.983664775 +0300
+++ /tmp/Makefile   2012-06-28 15:25:03.0 +0300
@@ -153,6 +153,7 @@
 
 CVS?= cvs
 SUP?= csup
+GIT?= git
 PORTSNAP?= portsnap
 PORTSNAP_FLAGS?= -p ${.CURDIR}
 .if defined(SUPHOST)
@@ -170,6 +171,15 @@
@echo  Updating ${.CURDIR} from cvs repository ${CVSROOT}
@echo --
cd ${.CURDIR}; ${CVS} -R -q update -A -P -d -I!
+.elif defined(GIT_UPDATE)
+   @echo --
+   @echo  Updating ${.CURDIR} from GIT+SVN repository ${CVSROOT}
+   @echo --
+.if !exists(${PORTSDIR}/.git)
+   cd ${.CURDIR}; ${GIT} svn rebase
+.else
+   ${GIT} svn clone -$(svn log -q --limit 1 $SVN_ROOT | awk '/^r/{print
$1}') $SVN_ROOT
+.endif
 .else
@echo --
@echo  Running ${PORTSNAP}


On Wed, 2012-06-27 at 17:30 +, Thomas Abthorpe wrote:
 The FreeBSD ports tree will migrate from CVS to Subversion soon. The
 anticipated date for the migration is July 14th. This will have no impact
 for ports tree users as there will be a SVN to CVS exporter.
 
 Please note that cvsup will still work after the migration. Nevertheless
 c(v)sup is pretty dated so you may want to see if portsnap(8) will fit your
 needs.
 
 Beat and Thomas
 on behalf of portmgr@
 
 http://blogs.freebsdish.org/portmgr/2012/06/27/ports-tree-migration-to-subversion/
 ___
 freebsd-ports@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: [HEADS UP] Ports tree migration to Subversion

2012-06-28 Thread Eitan Adler
On 28 June 2012 05:33, mbsd m...@isgroup.com.ua wrote:
 Hi list.

 It will be wonderful. When src had moved to svn, nobody cared about make
 update command.
 I wish to had this in ports makefile:

Submit a PR with this patch so portmgr will look at it.


-- 
Eitan Adler
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: [HEADS UP] Ports tree migration to Subversion

2012-06-28 Thread mbsd
Ok.

I'll be submitting a pr when ports move to svn.
Without testing, this patch is not more than dirty code.

On Thu, 2012-06-28 at 07:55 -0700, Eitan Adler wrote:
 On 28 June 2012 05:33, mbsd m...@isgroup.com.ua wrote:
  Hi list.
 
  It will be wonderful. When src had moved to svn, nobody cared about make
  update command.
  I wish to had this in ports makefile:
 
 Submit a PR with this patch so portmgr will look at it.
 
 


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


portmaster pkgng patch in portmaster/files?

2012-06-28 Thread Anton Shterenlikht
A request to pkgng team and/or dougb
(feel free to ignore if you think
it's unreasonable).

Please add the portmaster pkgng patch
to portmaster/files, to be triggered
by WITH_PKGNG=yes in /etc/make.conf.

I often forget to pull the latest patch
from the git page, when updating portmaster.
This change would save some time/frustration.

Thanks

-- 
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)117 331 5944
Fax: +44 (0)117 929 4423
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: portmaster pkgng patch in portmaster/files?

2012-06-28 Thread Chris Rees
On 28 June 2012 23:09, Anton Shterenlikht me...@bristol.ac.uk wrote:
 A request to pkgng team and/or dougb
 (feel free to ignore if you think
 it's unreasonable).

 Please add the portmaster pkgng patch
 to portmaster/files, to be triggered
 by WITH_PKGNG=yes in /etc/make.conf.

 I often forget to pull the latest patch
 from the git page, when updating portmaster.
 This change would save some time/frustration.

The portmaster maintainer is reluctant to add 'official' support for
pkgng until he has tested it thoroughly, which I understand is on his
todo list (an understandable position, given the complexity).

Perhaps I could suggest that you try out poudriere package sets in the
meantime? You'll find it very fast, and discover the real power of
pkgng.

http://blog.etoilebsd.net/post/Home_made_pkgng_repo

Chris
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


msgmerge hangs

2012-06-28 Thread Conrad J. Sabatier
I've been noticing for a while now in my
port builds that /usr/local/bin/msgmerge has a distinct tendency to get
hung up, just sitting there spinning its wheels forever.

Has anyone else ever seen this behavior, or know what may be causing it
and how to correct it?

Thanks!

-- 
Conrad J. Sabatier
conr...@cox.net
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: RFE - FreeBSD Port: zfs-snapshot-mgmt-20090201_2

2012-06-28 Thread Andriy Gapon
on 28/06/2012 11:16 Karli Sjöberg said the following:
 Hi!
 
 I am a storage-technician working at the Swedish University of Agriculture 
 and we are using zfs-snapshot-mgmt to create scheduled snapshots, but are 
 failing on our disaster-recovery machine because of:
 
 /usr/local/bin/zfs-snapshot-mgmt:130:in `join': can't convert nil into String 
 (TypeError)
 from /usr/local/bin/zfs-snapshot-mgmt:130:in `snapshots'
 from /usr/local/bin/zfs-snapshot-mgmt:137:in `snapshots_to_remove'
 from /usr/local/bin/zfs-snapshot-mgmt:145:in `remove_snapshots'
 from /usr/local/bin/zfs-snapshot-mgmt:213
 from /usr/local/bin/zfs-snapshot-mgmt:210:in `each'
 from /usr/local/bin/zfs-snapshot-mgmt:210
 
 Now, since this is a disaster-recovery unit, I would rather not have to have 
 all filesystems mounted for the script to function as we have many servers 
 with many file systems backing up towards this unit, which would result in 
 quite alot of mounts that are completely unnecessary to the backup server 
 itself. I also consider it a potential security risk having all these file 
 systems, from all of these different machines mounted in the same 
 place(server). I mean, if someone would like to steal as much valuable data 
 as possible, why crack hundreds of servers and steal it piece by piece when 
 you could just crack one and have it all, right? That doesn´t really make 
 sense because if someone were to crack the backup server they could just 
 mount all filesystems themselves, but only if they knew they were there. But 
 also having them mounted feels like just handing it to them.
 
 Unfortunately I know nothing about programming so I can´t be of any help, 
 besides testing patches, but do you think this can be done? Change the script 
 so that it doesn´t require the file systems to be mounted for it to be able 
 to take snapshots?

How about this?

--- zfs-snapshot-mgmt   2010-06-02 05:31:28.759931924 +0300
+++ zfs-snapshot-mgmt   2010-06-01 01:49:46.665034414 +0300
@@ -127,8 +127,10 @@
   end

   def snapshots(prefix)
-path = File.join(@mount_point, '.zfs', 'snapshot')
-Dir.open(path).select do |name|
+#path = File.join(@mount_point, '.zfs', 'snapshot')
+#Dir.open(path).select do |name|
+s = IO.popen('zfs list -r -t snapshot -H -o name ' +
@name).readlines.collect.select { |item| item[0, @name.length + 1] == @name +
'@' }.map { |item| item[@name.length + 1 .. -1] }
+s.select do |name|
   name[0, prefix.length] == prefix
 end.map { |name| SnapshotInfo.new(name, @name, prefix) }
   end



-- 
Andriy Gapon

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: [HEADS UP] Ports tree migration to Subversion

2012-06-28 Thread Jason Hellenthal


On Wed, Jun 27, 2012 at 03:11:30PM -0700, Kevin Oberman wrote:
 On Wed, Jun 27, 2012 at 2:52 PM, Jason Helfman jhelf...@e-e.com wrote:
  On Wed, Jun 27, 2012 at 02:47:34PM -0700, Kevin Oberman thus spake:
 
  On Wed, Jun 27, 2012 at 10:30 AM, Thomas Abthorpe tabtho...@freebsd.org
  wrote:
 
  The FreeBSD ports tree will migrate from CVS to Subversion soon. The
  anticipated date for the migration is July 14th. This will have no impact
  for ports tree users as there will be a SVN to CVS exporter.
 
  Please note that cvsup will still work after the migration. Nevertheless
  c(v)sup is pretty dated so you may want to see if portsnap(8) will fit
  your
  needs.
 
  Beat and Thomas
  on behalf of portmgr@
 
 
  http://blogs.freebsdish.org/portmgr/2012/06/27/ports-tree-migration-to-subversion/
 
 
  While portsnap has several advantages over csup, it is unusable in my
  case because I have always maintained local mods to ports in the ports
  tree and portsnap neatly removes them. I may move to using svn to
  maintain my own copy of the tree and update the working directory
  where I can keep my customizations.
 
 
  You may want to look at the manpage for portsnap.conf and see how
  advantageous it may be to use the REFUSE option.
 
 That an excellent idea. I was thinking that, since I keep my private
 patches in the files directory and let the normal 'make patch' apply
 them, that it would still delete them, but careful reading of the man
 page implies that I could list these file (paths) as REFUSED and
 portsnap would leave them alone.
 
 I'll experiment and see of this works. If so, I can move away from csup.
 

In any event it may be more resourcful just to go to SVN as the
advantages of that cannot be taken if something like portsnap or csup is
used.

Updating
Diffing
Committing
Stating
Reverting

I am sure the list of 'ing goes on and on.


-- 

 - (2^(N-1))
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: [HEADS UP] Ports tree migration to Subversion

2012-06-28 Thread Jason Hellenthal


On Thu, Jun 28, 2012 at 06:45:20PM +0300, mbsd wrote:
 Ok.
 
 I'll be submitting a pr when ports move to svn.
 Without testing, this patch is not more than dirty code.
 
 On Thu, 2012-06-28 at 07:55 -0700, Eitan Adler wrote:
  On 28 June 2012 05:33, mbsd m...@isgroup.com.ua wrote:
   Hi list.
  
   It will be wonderful. When src had moved to svn, nobody cared about make
   update command.
   I wish to had this in ports makefile:
  
  Submit a PR with this patch so portmgr will look at it.
  

How do you propose it should define a OOB repo ? since there is no
official ... repo for git.

Yes I know! there are some out there. But thats not to say they should
be supported in tree until one has at least been announced as official
and can be pointed to and has shown to be kept just as up to date as the
svn tree.

JMO

-- 

 - (2^(N-1))
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: [HEADS UP] Ports tree migration to Subversion

2012-06-28 Thread Bryan Drewery
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 6/28/2012 7:25 PM, Jason Hellenthal wrote:
 
 
 On Thu, Jun 28, 2012 at 06:45:20PM +0300, mbsd wrote:
 Ok.

 I'll be submitting a pr when ports move to svn.
 Without testing, this patch is not more than dirty code.

 On Thu, 2012-06-28 at 07:55 -0700, Eitan Adler wrote:
 On 28 June 2012 05:33, mbsd m...@isgroup.com.ua wrote:
 Hi list.

 It will be wonderful. When src had moved to svn, nobody cared about make
 update command.
 I wish to had this in ports makefile:

 Submit a PR with this patch so portmgr will look at it.

 
 How do you propose it should define a OOB repo ? since there is no
 official ... repo for git.
 
 Yes I know! there are some out there. But thats not to say they should
 be supported in tree until one has at least been announced as official
 and can be pointed to and has shown to be kept just as up to date as the
 svn tree.
 
 JMO
 

The proposed patch is for git-svn. It checks out from the *official* SVN
as a local git repository. It requires no git repository to be
maintained by anyone but the person who checks it out.

Regards,
Bryan Drewery

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJP7QTxAAoJEG54KsA8mwz50ZsP/jm6/hrboW3e4lzDAUVcF+yT
fZ+5dv5Ra+AhyPDii255G7NrnB9jQsbK3F2oxGYBb3OpPvqYjgTxtTBbEYgSr6EJ
z5TJGjNBLrr+kGAxu2/pWp1/yF1VFoHz6/8ScSl+yJyshGLUXI9B0S6GeivubJ0F
SHq7HyPSjNGMlcLcw2UXGvbSIfargAw0VU+nQajoIvDx/C/VHaH8Gyp6rVkAcGv3
QrfWqjIGsLaqPxJrKRA0b1HoQPcJ/hqXPe+koANdMaHbombDyVpr9G2lzmpWUL4Y
1m6uDy6lboH+dkaaYxk9GFZ/c4xjialmfTfQoUVBW/au5huHbivFfZb0jSJ6IuLa
WinVl5HyBIZ0XXiBNz/rofLj7QQQC/5HRiyjhsKHkmmD1ZwvwFAYjoPzXa/PoMF3
j/xaAv+hmLFirA0vGTUQlJpU8L3C9S+20Y7T1hUffGX0cgWe1voXtQL1p0kUo2Ug
tTTWKiuNWay0M31v8UwpdyeUHloqcVahG7nlikH1kexgL4nr6xKaIX+TEWp/eoqg
TaOBTiZPVXmVUC2u3WSIF1Ho30ofOd7zXRvsPnRY4vMef+PNAOqYjSUKH4u+rGP7
0qT+GdRV4ERturlYuPb3yswAP+aAJ5Gq7TOJg34JPGn3OndhFnZvxvEG1IjkSwjG
gNuKArDfwVQdGzMZCXD2
=IpdS
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: [HEADS UP] Ports tree migration to Subversion

2012-06-28 Thread mbsd
I have been using git svn rebase for src since src moved on git.
I think new options SVN_UPDATE and probably GIT_UPDATE :) in make.conf
are good idea.

On Thu, 2012-06-28 at 20:29 -0500, Bryan Drewery wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 On 6/28/2012 7:25 PM, Jason Hellenthal wrote:
  
  
  On Thu, Jun 28, 2012 at 06:45:20PM +0300, mbsd wrote:
  Ok.
 
  I'll be submitting a pr when ports move to svn.
  Without testing, this patch is not more than dirty code.
 
  On Thu, 2012-06-28 at 07:55 -0700, Eitan Adler wrote:
  On 28 June 2012 05:33, mbsd m...@isgroup.com.ua wrote:
  Hi list.
 
  It will be wonderful. When src had moved to svn, nobody cared about make
  update command.
  I wish to had this in ports makefile:
 
  Submit a PR with this patch so portmgr will look at it.
 
  
  How do you propose it should define a OOB repo ? since there is no
  official ... repo for git.
  
  Yes I know! there are some out there. But thats not to say they should
  be supported in tree until one has at least been announced as official
  and can be pointed to and has shown to be kept just as up to date as the
  svn tree.
  
  JMO
  
 
 The proposed patch is for git-svn. It checks out from the *official* SVN
 as a local git repository. It requires no git repository to be
 maintained by anyone but the person who checks it out.
 
 Regards,
 Bryan Drewery
 
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.10 (MingW32)
 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
 
 iQIcBAEBAgAGBQJP7QTxAAoJEG54KsA8mwz50ZsP/jm6/hrboW3e4lzDAUVcF+yT
 fZ+5dv5Ra+AhyPDii255G7NrnB9jQsbK3F2oxGYBb3OpPvqYjgTxtTBbEYgSr6EJ
 z5TJGjNBLrr+kGAxu2/pWp1/yF1VFoHz6/8ScSl+yJyshGLUXI9B0S6GeivubJ0F
 SHq7HyPSjNGMlcLcw2UXGvbSIfargAw0VU+nQajoIvDx/C/VHaH8Gyp6rVkAcGv3
 QrfWqjIGsLaqPxJrKRA0b1HoQPcJ/hqXPe+koANdMaHbombDyVpr9G2lzmpWUL4Y
 1m6uDy6lboH+dkaaYxk9GFZ/c4xjialmfTfQoUVBW/au5huHbivFfZb0jSJ6IuLa
 WinVl5HyBIZ0XXiBNz/rofLj7QQQC/5HRiyjhsKHkmmD1ZwvwFAYjoPzXa/PoMF3
 j/xaAv+hmLFirA0vGTUQlJpU8L3C9S+20Y7T1hUffGX0cgWe1voXtQL1p0kUo2Ug
 tTTWKiuNWay0M31v8UwpdyeUHloqcVahG7nlikH1kexgL4nr6xKaIX+TEWp/eoqg
 TaOBTiZPVXmVUC2u3WSIF1Ho30ofOd7zXRvsPnRY4vMef+PNAOqYjSUKH4u+rGP7
 0qT+GdRV4ERturlYuPb3yswAP+aAJ5Gq7TOJg34JPGn3OndhFnZvxvEG1IjkSwjG
 gNuKArDfwVQdGzMZCXD2
 =IpdS
 -END PGP SIGNATURE-
 ___
 freebsd-ports@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org