How can I create a disk partition on a disk that is greater than 2TB in size?

• The fdisk command only supports the legacy MBR partition table format (also known as msdos partition table)
  
  • MBR partition table do not support disks greater than 2.1TB, and therefore fdisk is also unable to create partition tables on these devices.
  • Note that some older versions of fdisk may permit a larger size to be created but the resulting partition table will be invalid.
• The parted command can create disk labels using MBR (msdos), GUID Partition Table (GPT), SUN disk labels and many more types.
  
  • The GPT disk label overcomes many of the limitations of the DOS MBR including restrictions on the size of the disk, the size of any one partition and the overall number of partitions.
  • Note that booting from a GPT labelled volume requires firmware support and this is not commonly available on non-EFI platforms (including x86 and x86_64 architectures).
  
  Procedure:
  
• Use the parted tool to access the partition table of the device:
  

  # parted /dev/sdj
  Using /dev/sdj
  Welcome to GNU Parted! Type 'help' to view a list of commands.
  (parted)

• Once at the parted prompt, create a GPT label on the disk:
  

  (parted) mklabel
  Warning: The existing disk label on /dev/sdj will be destroyed and all data on this disk will be lost. Do you want to continue?
  Yes/No? Yes                                                                 
  New disk label type?  [gpt]? gpt                                          
  (parted)

  Note: This will remove any existing partition table and partitions on the device.

• Use the print command to show the size of the disk as reported by parted.  We need this later:

  (parted) print                                                            
  
  Model: Linux device-mapper (dm)
  Disk /dev/sdj: 5662310.4MB
  Sector size (logical/physical): 512B/512B
  Partition Table: gpt
  
  Number  Start  End  Size  File system  Name  Flags

• Create a primary partition on the device.  In this example, the partition will encompass the entire disk (using size from the step above):
  

  (parted) mkpart primary 0 5662310.4MB

• Unlike fdisk, you do not have to write out the partition table changes with parted.  Display your new partition and quit.
  

  (parted) print
  
  Model: Linux device-mapper (dm)
  Disk /dev/mapper/VolGroup00-gpttest: 5662310.4MB
  Sector size (logical/physical): 512B/512B
  Partition Table: gpt
  
  Number  Start   End          Size         File system  Name     Flags
   1      17.4kB  5662310.4MB  5662310.4MB               primary       
  
  (parted) quit                                                             
  Information: Don't forget to update /etc/fstab, if necessary.

• You can now create a filesystem on the device /dev/sdj1

How a Web Browser Works?

Add caption

Which communication ports does Symantec Endpoint Protection 11.0 use?

The Symantec Endpoint Protection Manager (SEPM) use two web servers: Internet Information Services (IIS) and Tomcat. IIS uses port 80 (or 8014) and 443 - Tomcat uses port 9090 and 8443. The communication between IIS and Tomcat uses the HTTP protocol. IIS uses port 9090 to talk to Tomcat, Tomcat uses port 80 to talk to IIS.


Client-Server Communication:
For IIS SEP uses HTTP or HTTPS between the clients or Enforcers and the server. For the client server communication it uses port 80 (or 8014) and 443 by default. In addition, the Enforcers use RADIUS to communicate in real-time with the manager console for clients authentication. This is done on UDP port 1812.


Remote Console:
9090 is used by the remote console to download .jar files and display the help pages.
8443 is used by the remote console to communicate with SEPM and the Replication Partners to replicate data.

Client-Enforcer Authentication:

The clients communicate with the Enforcer using a proprietary communication protocol. This communication uses a challenge-response to authenticate the clients. The default port for this is UDP 39,999.

View System Logs Live

If you want to monitor the system logs in a live environment, you can use the tail command with an option -f or -F.
This will work in any Linux/UNIX environment.
To exit from the view, you can use Ctrl + C. The same option can be used with any text based files to find the updation to the file in live environment.

Usage:

# tail -f /var/log/messages

or

# tail -F /var/adm/messages


tail -f will work as long as the underlying file we’re trying to read doesn’t change. If you’re trying to read a link to a file and the original file (and thus the link) changes, tail -f will not work.

For that reason, its better to use tail -F for such files as described above … or tail -f –retry