Should I use a CoW filesystem on my PC if I only wanted snapshot capabilities ? Post: 303045124

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Unix Capabilities?

We are looking into buying a new software, billing software that is, and want to know if you can run that on the same UNIX server as another major software? Is there a limit to the different types of software Unix can run, or is it like windows where you can install as many as you like? ...

2. UNIX for Advanced & Expert Users

p570 Capabilities

Hi there. I've been tasked with making a new design for our Unix systems :eek: Now the question I have is; How many LPARs can a p570 hold WITHOUT using a VIO Server. Many Thanks Kees

3. Red Hat

Adding capabilities to an RPM

Hi. I downloaded a package that could only be installed on RHEL5, and not 4 or 3, so I got the source in order to compile it on RHEL 3 so hopefully it will work on all versions. So I have the source for a working package, but when I build it in RHEL 3 and then try to install it in RHEL 5, it...

4. Filesystems, Disks and Memory

Wanted: Geographically distributed filesystem solution

I'm looking for a means to ensure that servers in the two or three datacenters, connected in a ring via IP through two ISPs, can distribute load and/or replicate data among at least two SAN-class disk devices. I want to evaluate several solutions, and I'm open to solutions ranging from free,...

5. Solaris

Cannot use filesystem while sending a snapshot

I've got a Solaris 11 Express installed on my machine. I have created a raidz2 zpool named shares and a simple one-disc zpool named backup. I have made a script that would send a daily snapshot of shares to backup. I use these commands zfs snapshot shares@DDMMRRRRHHMM zfs send -i shares@.......

6. UNIX for Advanced & Expert Users

Use of Capabilities

I wonder if anyone could assist with some problems I'm having with Linux Capabilities and their use when using the commands "nice" and "schedtool". I run a couple of PCs, one is an elderly AMD Sempron 2800+ (32-bit, 2GHz clock and 3GB memory) that is used as a family multimedia system running...

7. Linux

Broadcom under Fedora 18 (Spherical Cow)

So I'm having a problem getting a Broadcom BCM4312 wireless controller to work under the broadcom-wl module $uname Linux 3.8.11-200.fc18.x86_64 #1 SMP Wed May 1 19:44:27 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux lspci -v 05:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g...

8. UNIX for Advanced & Expert Users

Linux capabilities discussion

Hi I'm trying to compile my linux kernel with CONFIG_SECURITY_CAPABILITIES=y. any idea what this thing does ?? Also another question , If I compile the kernel that I'm currently using , what'll happen ? ~cheers

9. What is on Your Mind?

Anybody want to talk about Dirty Cow?

Hi All, How worried is everyone about the Dirty Cow Linux exploit? Has anybody experienced attacks yet? From the research I've done it seems that the exploit is "reliable" (that is it works nearly every time on vulverable systems) which is not good news. We all believe that Unix/Linux...

LEARN ABOUT DEBIAN

pegasus-remove

PEGASUS-REMOVE(1)														 PEGASUS-REMOVE(1)

NAME

       pegasus-remove - removes a workflow that has been planned and submitted using pegasus-plan and pegasus-run

SYNOPSIS

       pegasus-remove [-d dagid] [-v] [rundir]

DESCRIPTION

       The pegasus-remove command remove a submitted/running workflow that has been planned and submitted using pegasus-plan and pegasus-run. The
       command can be invoked either in the planned directory with no options and arguments or just the full path to the run directory.

OPTIONS

       By default pegasus-remove does not require any options or arguments if invoked from within the planned workflow directory. If running the
       command outside the workflow directory then a full path to the workflow directory needs to be specified or the dagid of the workflow to be
       removed.

       pegasus-remove takes the following options:

       -d dagid, --dagid dagid
	   The workflow dagid to remove

       -v, --verbose
	   Raises debug level. Each invocation increase the level by 1.

       rundir
	   Is the full qualified path to the base directory containing the planned workflow DAG and submit files. This is optional if
	   pegasus-remove command is invoked from within the run directory.

RETURN VALUE

       If the workflow is removed successfully pegasus-remove returns with an exit code of 0. However, in case of error, a non-zero exit code
       indicates problems. An error message clearly marks the cause.

FILES

       The following files are opened:

       braindump
	   This file is located in the rundir. pegasus-remove uses this file to find out paths to several other files.

ENVIRONMENT VARIABLES

       PATH
	   The path variable is used to locate binary for condor_rm.

SEE ALSO

       pegasus-plan(1), pegasus-run(1)

AUTHORS

       Gaurang Mehta <gmehta at isi dot edu>

       Jens-S. Vockler <voeckler at isi dot edu>

       Pegasus Team http://pegasus.isi.edu

								    05/24/2012							 PEGASUS-REMOVE(1)