01-12-2011
OK, thanks.
If using the CLI is required I'm going to need a new set of instructions to follow.
How do you display physical drives available for the pool? All the instruction I'm finding assume you already know what your drives are called (and they are not "C:, D:" as in windows, nor are they "/mnt/hda1, hda2" or "/media/sda1, sda2"as they are in linux)?
---------- Post updated at 08:15 PM ---------- Previous update was at 08:06 PM ----------
OK, great! Thanks dbtrade!
Found it no problem. To answer my own question "format" looks like it will do the trick. Those instructions are a lot better (for beginners) than the others I've found.
Thanks again.
9 More Discussions You Might Find Interesting
1. Solaris
Hi, I am nowusing ZFS since some weeks and now I have 2 questions:
1) in zpool I saw some disk added with the *s2 at the end, I have in mind that should not be ? is this right and if so can I get the *s2 disk out of the zpool ?
2) Zpool has still 2 spare disk but when I try to create a new... (6 Replies)
Discussion started by: manni2
6 Replies
2. Solaris
while using oracle solaris live upgrade it is mentioned to set few mountpoints like that.. what is the point doing that. (1 Reply)
Discussion started by: chidori
1 Replies
3. UNIX for Advanced & Expert Users
Hello,
I am using Ubuntu Linux and having problems in setting up remote syslogging. Appreciate your help on this.
On the server unix host, I have made following changes.
uncommented following lines in /etc/rsyslog.conf
$ModLoad imudp
$UDPServerRun 514
Now i am trying to run rsyslog in... (0 Replies)
Discussion started by: ravi.videla
0 Replies
4. Solaris
I 'm trying to clone a zfs file system pool/u01 to a new file system called newpool/u01 using following commands
zfs list
zfs snapshot pool/u01@new
zfs send pool/u01@new | zfs -F receive newpool/u01
Its a 100G file system snapshot and copied to same server on different pool and... (9 Replies)
Discussion started by: fugitive
9 Replies
5. Solaris
Short version:
pfexec zpool scrub rpool fails saying I do not have permission to perform that action. Apparently scrub is not one of the pfexec allowed actions. Any idea on how to get around it?
Long version:
I got tired of manually running scrubs and am trying to set it to happen... (4 Replies)
Discussion started by: taltamir
4 Replies
6. Solaris
I have two servers, we'll call them sv1 and sv2.
both are Solaris 11.1 LDOMS running on a T4-4 with RBAC enabled.
my user has zfs allow send, receive on both servers and has ssh keys shared.
on sv2 (the destination) I have a zpool called zones that has no zfs fs built
on sv1 (the source) I... (5 Replies)
Discussion started by: os2mac
5 Replies
7. Solaris
Hello All
I’ve made the decision to switch my storage server from FreeNAS to Solaris. I opted to use FreeNAS as it has ZFS and until BTRFS is stable, it’s the best option (IMHO) for backup and network storage.
The switch was facilitated by the USB stick that FreeNAS was on got lost during a... (1 Reply)
Discussion started by: BlueDalek
1 Replies
8. Proxy Server
Hello,
I am having issues setting the "read-only" flag via Windows Explorer on my AIX Samba share...
I have on my AIX 7.1 system installed Samba 3.6.24 and configured, joined to our Windows domain successfully.
The samba binaries I got from perzl.org/aix
In my smb.conf I have...
... (1 Reply)
Discussion started by: c3rb3rus
1 Replies
9. Shell Programming and Scripting
Hi,
I have set alias rm='rm -i' and i m able to see that in the list of aliases.
however, when i fire the rm command the '-i' interactive flag does not seem to kick in.
I login to a free online terminal and then i say bash to set the bash profile.
Join
Here is the output... (27 Replies)
Discussion started by: mohtashims
27 Replies
LEARN ABOUT LINUX
tcprules
tcprules(1) General Commands Manual tcprules(1)
NAME
tcprules - compile rules for tcpserver
SYNOPSIS
tcprules rules.cdb rules.tmp
OVERVIEW
tcpserver optionally follows rules to decide whether a TCP connection is acceptable. For example, a rule of
18.23.0.32:deny
prohibits connections from IP address 18.23.0.32.
tcprules reads rules from its standard input and writes them into rules.cdb in a binary format suited for quick access by tcpserver.
tcprules can be used while tcpserver is running: it ensures that rules.cdb is updated atomically. It does this by first writing the rules
to rules.tmp and then moving rules.tmp on top of rules.cdb. If rules.tmp already exists, it is destroyed. The directories containing
rules.cdb and rules.tmp must be writable to tcprules; they must also be on the same filesystem.
If there is a problem with the input, tcprules complains and leaves rules.cdb alone.
The binary rules.cdb format is portable across machines.
RULE FORMAT
A rule takes up one line. A file containing rules may also contain comments: lines beginning with # are ignored.
Each rule contains an address, a colon, and a list of instructions, with no extra spaces. When tcpserver receives a connection from that
address, it follows the instructions.
ADDRESSES
tcpserver starts by looking for a rule with address TCPREMOTEINFO@TCPREMOTEIP. If it doesn't find one, or if TCPREMOTEINFO is not set, it
tries the address TCPREMOTEIP. If that doesn't work, it tries shorter and shorter prefixes of TCPREMOTEIP ending with a dot. If none of
them work, it tries the empty string.
For example, here are some rules:
joe@127.0.0.1:first
18.23.0.32:second
127.:third
:fourth
::1:fifth
If TCPREMOTEIP is 10.119.75.38, tcpserver will follow the fourth instructions.
If TCPREMOTEIP is ::1, tcpserver will follow the fifth instructions. Note that you cannot detect IPv4 mapped addresses by matching
"::ffff", as those addresses will be converted to IPv4 before looking at the rules.
If TCPREMOTEIP is 18.23.0.32, tcpserver will follow the second instructions.
If TCPREMOTEINFO is bill and TCPREMOTEIP is 127.0.0.1, tcpserver will follow the third instructions.
If TCPREMOTEINFO is joe and TCPREMOTEIP is 127.0.0.1, tcpserver will follow the first instructions.
ADDRESS RANGES
tcprules treats 1.2.3.37-53:ins as an abbreviation for the rules 1.2.3.37:ins, 1.2.3.38:ins, and so on up through 1.2.3.53:ins. Similarly,
10.2-3.:ins is an abbreviation for 10.2.:ins and 10.3.:ins.
INSTRUCTIONS
The instructions in a rule must begin with either allow or deny. deny tells tcpserver to drop the connection without running anything.
For example, the rule
:deny
tells tcpserver to drop all connections that aren't handled by more specific rules.
The instructions may continue with some environment variables, in the format ,VAR="VALUE". tcpserver adds VAR=VALUE to the current envi-
ronment. For example,
10.0.:allow,RELAYCLIENT="@fix.me"
adds RELAYCLIENT=@fix.me to the environment. The quotes here may be replaced by any repeated character:
10.0.:allow,RELAYCLIENT=/@fix.me/
Any number of variables may be listed:
127.0.0.1:allow,RELAYCLIENT="",TCPLOCALHOST="movie.edu"
SEE ALSO
tcprulescheck(1), tcpserver(1), tcp-environ(5)
tcprules(1)