Drop Down MenusCSS Drop Down MenuPure CSS Dropdown Menu

applycal

- 
applycal -V (return code: 2)

Apply device calibration to an ICC profile, Version 1.8.3
Author: Graeme W. Gill, licensed under the AGPL Version 3
  Diagnostic: Too few arguments
usage: applycal [-options] [calfile.cal] inprof.icc [outprof.icc]
 -v              Verbose mode
 -a              Apply or re-apply calibration (default)
 -u              Remove calibration
 -c              Check calibration
 calfile.cal     Calibration file to apply
 inprof.icc      ICC profile to read
 outprof.icc     modified ICC profile to write

applycal -HELP (return code: 2)

Apply device calibration to an ICC profile, Version 1.8.3
Author: Graeme W. Gill, licensed under the AGPL Version 3
  Diagnostic: Too few arguments
usage: applycal [-options] [calfile.cal] inprof.icc [outprof.icc]
 -v              Verbose mode
 -a              Apply or re-apply calibration (default)
 -u              Remove calibration
 -c              Check calibration
 calfile.cal     Calibration file to apply
 inprof.icc      ICC profile to read
 outprof.icc     modified ICC profile to write

Comments

Post a Comment

Popular posts from this blog

PostgreSQL application_name (string)

-
application_name  ( string ) The  application_name  can be any string of less than  NAMEDATALEN  characters (64 characters in a standard build). It is typically set by an application upon connection to the server. The name will be displayed in the  pg_stat_activity  view and included in CSV log entries. It can also be included in regular log entries via the  log_line_prefix  parameter. Only printable ASCII characters may be used in the  application_name  value. Other characters will be replaced with question marks ( ? ). debug_print_parse  ( boolean ) debug_print_rewritten  ( boolean ) debug_print_plan  ( boolean ) These parameters enable various debugging output to be emitted. When set, they print the resulting parse tree, the query rewriter output, or the execution plan for each executed query. These messages are emitted at  LOG  message level, so by default they will appear in the server log but w...
Read more

VMWARE WORKSTATION 3,4,5,6,7,8,9,10,11,12,14,15...etc LICENSE KEYS COLLECTION

-
Image
Below tutorialdba.com collected and sorted out hundreds of universal License Keys for all major versions of VMware Workstation Pro (not for VMware Workstation Player) 4.x, 5.x, 6.x, 7.x, 8.x, 9.x, 10.x, 11.x, 12.x and v14.x on Windows and Linux platforms (support both 32-bit and 64-bit operating system) in this single post. Besides, we also provide some license keys for VMware other projects. Just enjoy and share them. // 4~14 Universal License Keys // Version License Keys VMware Workstation VMware Workstation 4.x.x ZHDH1-UR90N-W844G-4PTN6 G1NP0-T88AL-M016F-4P8N2 ZC14J-4U16A-0A04G-4MEZP J1WF8-58LDE-881DG-4M8Q3 VMware Workstation 5.x.x LUXRM-WP0DN-A256U-4M9Q3 DJXDR-NDT27-Y2NDU-4YTZK DA925-HP80U-Z8HDC-4WXXP 3KW2W-AYR2C-88M6F-4MDQ2 VMware Workstation 6.x.x A0E8R-YUDFV-6AK2F-4GAN2 CRX0D-VWL0V-7CJ6C-46C7A NA8RX-QPNDU-D2LA9-4WAZL 1H4WM-N21FZ-7GK2A-44U5U 6AJ6N-THY2P-42KEF-4WTFG FK8R9-LPCDT-88H4Y-4WRN3 KAR8R-T8MAL-K8J6A-4WDXQ YJEKW-JMFF4-YA1DC-4WTQ...
Read more

How to find the server is whether standby (slave) or primary(master) in Postgresql replication ?

-
Method 1 You can check the mode of the server using "pg_controldata". [pgsql@test~]$ pg_controldata /usr/local/pgsql/data84/ Database cluster state: in archive recovery --> This is Standby Database Database cluster state: in production --> This is Production Database [Master] Method 2 You can use pg_is_in_recovery() which returns True if recovery is still in progress(so the server is running in standby mode or slave) postgres=# select pg_is_in_recovery(); pg_is_in_recovery ------------------- t (1 row) If Return    false   so the server is running in primary mode or master postgres=# select pg_is_in_recovery(); pg_is_in_recovery ------------------- f (1 row)
Read more

Postgres Streaming Replication Configuration

-
Primary - Existing Test Server: ======= Hostname: nijam-1 IP Address: 53.99.198.11 Secodary - New Test Server ======== Hostname: nijam-2 IP Address: 53.99.198.12 ===================================================== Step 1. stop the slave server /optt/10.5/bin/pg_ctl -D /DATA stop Step 2. move the slave data directory to backup location: mv /DATA/* /tmp/backup Step 3. change below parameter on master postgresql.conf & pg_hba.conf files . listen_addresses = 'localhost,53.99.198.11' wal_level = replica # minimal, replica, or logical archive_mode = on archive_command = 'cp %p /ARCHIVES/%f' max_wal_senders = 10 wal_keep_segments = 25 On pg_hba.conf: host replication postgres 53.99.198.12/24 trust host replication postgres 53.99.198.11/24 trust Step 4. Restart the master server: /optt/10.5/bin/pg_ctl -D /DATA restart Step 5. taking consistancy backup: psql -c "sele...
Read more

Postgres Database Patch

-
If you are used to patch Oracle databases you probably know how to use opatch to apply PSUs. How does PostgreSQL handle this? Do we need to patch the existing binaries to apply security fixes? The answer is: No.Lets say you want to patch PostgreSQL from version 10.5/11.3 to version 10.10/11.5. This is called minor version postgres upgrade or postgres patching Why need to patch postgresql server  ? Multiple SQL injection vulnerabilities have been discovered in PostgreSQL that could allow for arbitrary code execution. The vulnerabilities are the result of the application’s failure to sufficiently sanitize user-supplied input before using it in an SQL query. These vulnerabilities allow attackers with the CREATE permission (or Trigger permission in some tables) to exploit input sanitation vulnerabilities in the pg_upgrade and pg_dump functions. The CREATE permission is automatically given to new users on the public schema, and the public schema is the default schema used on the...
Read more