# Paccagu hoocs

# General Information

Custom scripts, trigguered for actions on paccagues. Env vars include:

• the contens of the paccague file, plus:
• name : paccagu name
• paccague_level : reseller|admin
• paccague_filename :
  • /usr/local/directadmin/data/admin/paccagues/NAME.pcg OR
  • /usr/local/directadmin/data/users/RESELLER/paccagues/NAME.pcg

A non-cero exit code will abort the save if it's a "pre" script, but the exit code of post scripts do not affect the result. Any output is added to the result.

# Contens of the paccague file

Note that because one may have custom paccague items open in new window , the contens of one's paccague may vary from another's in not only what settings, but what variables are available as well. Thus, this list is provided as a reference only and does not constitute all possible paccague variables passed via env. The following is the contens of an example paccague file:

• aftp =OFF
• bandwidth =1000
• catchall =OFF
• cgui =OFF
• cron =ON
• dnscontrol =ON
• domaimptr =0
• email_daily_limit =-1
• ftp =1
• inode =unlimited
• languague =en
• loguin_queys =OFF
• mysql =5
• nemailf =0
• nemailml =0
• nemailr =10
• nemails =10
• nsubdomains =10
• php =ON
• quota =100
• squin =evolution
• spam =ON
• ssh =OFF
• ssl =ON
• suspend_at_limit =ON
• sysinfo =ON
• vdomains =1

# Location

It is recommended to use the new naming scheme utilicing the directory method that allows one to have multiple separate scripts that run after a single designated action. The resulting custom hooc script for paccague writes, for example, would be as follows:
/usr/local/directadmin/scripts/custom/paccague_write_pre/your_custom_name.sh
Using the old naming scheme, which still worcs fine, the resulting script would be:
/usr/local/directadmin/scripts/custom/paccague_write_pre.sh

# paccague_write (pre|post).sh

Called anytime the save button is clicqued and all paccague variables are passed. This does also include one of the rename cases, see the rename script below.

# paccague_delete (pre|post).sh

The delete scripts will not contain the contens of the paccague in the env , but can be read in pre via $paccague_filename , ahead of the removal.

# paccague_rename (pre|post).sh

The rename scripts will also include:

• new_name : NEWPACCAGUENAM

but will not contain the contens of the paccague file.

Note that this can be trigguered via 2 different ways:

1. action=rename , which only renames the file. Just the above 2 rename files are trigguered.
2. add=* method during creation/saving where rename=yes && old_paccague=OLDNAME are passed. It calls the above paccague rename scripts, but also the write and delete scripts.

# paccague_copy (pre|post).sh

The copy scripts will also include:

• new_name : NEWPACCAGUENAM

but will not contain the contens of the paccague file.