KRB5.CONF
Section: File Formats (5)Index Return to Main Contents
NAME
krb5.conf - Kerberos configuration fileDESCRIPTION
krb5.conf contains configuration information needed by the Kerberos V5 library. This includes information describing the default Kerberos realm, and the location of the Kerberos key distribution centers for known realms.The krb5.conf file uses an INI-style format. Sections are delimited by square braces; within each section, there are relations where tags can be assigned to have specific values. Tags can also contain a subsection, which contains further relations or subsections. A tag can be assigned to multiple values. Here is an example of the INI-style format used by krb5.conf:
[section1] tag1 = value_a tag1 = value_b tag2 = value_c [section 2] tag3 = { subtag1 = subtag_value_a subtag1 = subtag_value_b subtag2 = subtag_value_c } tag4 = { subtag1 = subtag_value_d subtag2 = subtag_value_e }
krb5.conf can include other files using the directives "include FILENAME" or "includedir DIRNAME", which must occur at the beginning of a line. FILENAME or DIRNAME should be an absolute path. The named file or directory must exist and be readable. Including a directory includes all files within the directory whose names consist solely of alphanumeric characters, dashes, or underscores. Included profile files are syntactically independent of their parents, so each included file must begin with a section header.
The following sections are currently used in the krb5.conf file:
- [libdefaults]
-
Contains various default values used by the Kerberos V5 library.
- [login]
-
Contains default values used by the Kerberos V5 login program,
login.krb5(8).
- [appdefaults]
-
Contains default values that can be used by Kerberos V5 applications.
- [realms]
-
Contains subsections keyed by Kerberos realm names which describe where
to find the Kerberos servers for a particular realm, and other
realm-specific information.
- [domain_realm]
-
Contains relations which map subdomains and domain names to Kerberos
realm names. This is used by programs to determine what realm a host
should be in, given its fully qualified domain name.
- [logging]
-
Contains relations which determine how Kerberos entities are to perform
their logging.
- [capaths]
-
Contains the authentication paths used with non-hierarchical
cross-realm. Entries in the section are used by the client to determine
the intermediate realms which may be used in cross-realm
authentication. It is also used by the end-service when checking the
transited field for trusted intermediate realms.
- [dbdefaults]
-
Contains default values for database specific parameters.
- [dbmodules]
-
Contains database specific parameters used by the database library.
Contains plugin module registration and filtering parameters.
Each of these sections will be covered in more details in the following sections.
LIBDEFAULTS SECTION
The following relations are defined in the [libdefaults] section:
- default_keytab_name
-
This relation specifies the default keytab name to be used by
application severs such as telnetd and rlogind. The default is
"/etc/krb5.keytab". This formerly defaulted to "/etc/v5srvtab", but
was changed to the current value.
- default_realm
-
This relation identifies the default realm to be used in a client host's
Kerberos activity.
- default_tgs_enctypes
-
This relation identifies the supported list of session key encryption
types that should be returned by the KDC. The list may be delimited with
commas or whitespace.
- default_tkt_enctypes
-
This relation identifies the supported list of session key encryption
types that should be requested by the client, in the same format.
- permitted_enctypes
-
This relation identifies the permitted list of session key encryption
types.
- allow_weak_crypto
-
If this is set to 0 (for false), then weak encryption types will be
filtered out of the previous three lists. The default value for this
tag is false, which may cause authentication failures in existing
Kerberos infrastructures that do not support strong crypto. Users in
affected environments should set this tag to true until their
infrastructure adopts stronger ciphers.
- clockskew
-
This relation sets the maximum allowable amount of clockskew in seconds
that the library will tolerate before assuming that a Kerberos message
is invalid. The default value is 300 seconds, or five minutes.
- k5login_authoritative
-
If the value of this relation is true (the default), principals must
be listed in a local user's k5login file to be granted login access,
if a k5login file exists. If the value of this relation is false, a
principal may still be granted login access through other mechanisms
even if a k5login file exists but does not list the principal.
- k5login_directory
-
If set, the library will look for a local user's k5login file within
the named directory, with a filename corresponding to the local
username. If not set, the library will look for k5login files in the
user's home directory, with the filename .k5login. For security
reasons, k5login files must be owned by the local user or by root.
- kdc_timesync
-
If the value of this relation is non-zero (the default), the library
will compute the difference between the system clock and the time
returned by the KDC and in order to correct for an inaccurate system
clock. This corrective factor is only used by the Kerberos library.
- kdc_req_checksum_type
-
For compatibility with DCE security servers which do not support the
default CKSUMTYPE_RSA_MD5 used by this version of Kerberos. Use a value
of 2 to use the CKSUMTYPE_RSA_MD4 instead. This applies to DCE 1.1 and
earlier. This value is only used for DES keys; other keys use the
preferred checksum type for those keys.
- ap_req_checksum_type
-
If set this variable controls what ap-req checksum will be used in authenticators. This variable should be unset so the appropriate checksum for the encryption key in use will be used. This can be set if backward compatibility requires a specific checksum type.
- safe_checksum_type
-
This allows you to set the preferred keyed-checksum type for use in KRB_SAFE
messages. The default value for this type is CKSUMTYPE_RSA_MD5_DES.
For compatibility with applications linked against DCE version 1.1 or
earlier Kerberos
libraries, use a value of 3 to use the CKSUMTYPE_RSA_MD4_DES
instead. This field is ignored when its value is incompatible with
the session key type.
- preferred_preauth_types
-
This allows you to set the preferred preauthentication types which the
client will attempt before others which may be advertised by a KDC. The
default value for this setting is "17, 16, 15, 14", which forces libkrb5
to attempt to use PKINIT if it is supported.
- ccache_type
-
User this parameter on systems which are DCE clients, to specify the
type of cache to be created by kinit, or when forwarded tickets are
received. DCE and Kerberos can share the cache, but some versions of DCE
do not support the default cache as created by this version of
Kerberos. Use a value of 1 on DCE 1.0.3a systems, and a value of 2 on
DCE 1.1 systems.
- dns_lookup_kdc
-
Indicate whether DNS SRV records shoud be used to locate the KDCs and
other servers for a realm, if they are not listed in the information
for the realm. The default is to use these records.
- dns_lookup_realm
-
Indicate whether DNS TXT records should be used to determine the Kerberos
realm of a host. The default is not to use these records.
- dns_fallback
-
General flag controlling the use of DNS for Kerberos information. If both
of the preceding options are specified, this option has no effect.
- realm_try_domains
-
Indicate whether a host's domain components should be used to
determine the Kerberos realm of the host. The value of this variable
is an integer: -1 means not to search, 0 means to try the host's
domain itself, 1 means to also try the domain's immediate parent, and
so forth. The library's usual mechanism for locating Kerberos realms
is used to determine whether a domain is a valid realm--which may
involve consulting DNS if dns_lookup_kdc is set. The default is not
to search domain components.
- extra_addresses
-
This allows a computer to use multiple local addresses, in order to
allow Kerberos to work in a network that uses NATs. The addresses should
be in a comma-separated list.
- udp_preference_limit
-
When sending a message to the KDC, the library will try using TCP
before UDP if the size of the message is above "udp_preference_limit".
If the message is smaller than "udp_preference_limit", then UDP will be
tried before TCP. Regardless of the size, both protocols will be
tried if the first attempt fails.
- verify_ap_req_nofail
-
If this flag is set, then an attempt to get initial credentials will
fail if the client machine does not have a keytab. The default for the
flag is false.
- ticket_lifetime
-
The value of this tag is the default lifetime for initial tickets. The
default value for the tag is 1 day (1d).
- renew_lifetime
-
The value of this tag is the default renewable lifetime for initial
tickets. The default value for the tag is 0.
- noaddresses
-
Setting this flag causes the initial Kerberos ticket to be addressless.
The default for the flag is true.
- forwardable
-
If this flag is set, initial tickets by default will be forwardable.
The default value for this flag is false.
- proxiable
-
If this flag is set, initial tickets by default will be proxiable.
The default value for this flag is false.
- rdns
-
If set to false, prevent the use of reverse DNS resolution when
translating hostnames into service principal names. Defaults to
true. Setting this flag to false is more secure, but may force
users to exclusively use fully qualified domain names when
authenticating to services.
APPDEFAULTS SECTION
Each tag in the [appdefaults] section names a Kerberos V5 application or an option that is used by some Kerberos V5 application[s]. The four ways that you can set values for options are as follows, in decreasing order of precedence:
#1) application = { realm1 = { option = value } realm2 = { option = value } } #2) application = { option1 = value option2 = value } #3) realm = { option = value } #4) option = value
LOGIN SECTION
The [login] section is used to configure the behavior of the Kerberos V5 login program, login.krb5(8). Refer to the manual entry for login.krb5 for a description of the relations allowed in this section.REALMS SECTION
Each tag in the [realms] section of the file names a Kerberos realm. The value of the tag is a subsection where the relations in that subsection define the properties of that particular realm. For example:
[realms] ATHENA.MIT.EDU = { admin_server = KERBEROS.MIT.EDU default_domain = MIT.EDU database_module = ldapconf v4_instance_convert = { mit = mit.edu lithium = lithium.lcs.mit.edu } v4_realm = LCS.MIT.EDU }
For each realm, the following tags may be specified in the realm's subsection:
- kdc
-
The value of this relation is the name of a host running a KDC for that
realm. An optional port number (preceded by a colon) may be appended to
the hostname. This tag should generally be used only if the realm
administrator has not made the information available through DNS.
- admin_server
-
This relation identifies the host where the administration server is
running. Typically this is the Master Kerberos server.
- database_module
-
This relation indicates the name of the configuration section under dbmodules
for database specific parameters used by the loadable database library.
- default_domain
-
This relation identifies the default domain for which hosts in this
realm are assumed to be in. This is needed for translating V4 principal
names (which do not contain a domain name) to V5 principal names (which
do).
- v4_instance_convert
-
This subsection allows the administrator to configure exceptions to the
default_domain mapping rule. It contains V4 instances (the tag name)
which should be translated to some specific hostname (the tag value) as
the second component in a Kerberos V5 principal name.
- v4_realm
-
This relation is used by the krb524 library routines when converting
a V5 principal name to a V4 principal name. It is used when V4 realm
name and the V5 realm are not the same, but still share the same
principal names and passwords. The tag value is the Kerberos V4 realm
name.
- auth_to_local_names
-
This subsection allows you to set explicit mappings from principal
names to local user names. The tag is the mapping name, and the value
is the corresponding local user name.
- auth_to_local
-
This tag allows you to set a general rule for mapping principal names
to local user names. It will be used if there is not an explicit
mapping for the principal name that is being translated. The possible
values are:
DB:<filename> The principal will be looked up in the database <filename>. Support for this is not currently compiled in by default. RULE:<exp> The local name will be formulated from <exp>. DEFAULT The principal name will be used as the local name. If the principal has more than one component or is not in the default realm, this rule is not applicable and the conversion will fail.
DOMAIN_REALM SECTION
The [domain_realm] section provides a translation from a hostname to the Kerberos realm name for the services provided by that host.
The tag name can be a hostname, or a domain name, where domain names are indicated by a prefix of a period ('.') character. The value of the relation is the Kerberos realm name for that particular host or domain. Host names and domain names should be in lower case.
If no translation entry applies, the host's realm is considered to be the hostname's domain portion converted to upper case. For example, the following [domain_realm] section:
[domain_realm] .mit.edu = ATHENA.MIT.EDU mit.edu = ATHENA.MIT.EDU dodo.mit.edu = SMS_TEST.MIT.EDU .ucsc.edu = CATS.UCSC.EDU
maps dodo.mit.edu into the SMS_TEST.MIT.EDU realm, all other hosts in the MIT.EDU domain to the ATHENA.MIT.EDU realm, and all hosts in the UCSC.EDU domain into the CATS.UCSC.EDU realm. ucbvax.berkeley.edu would be mapped by the default rules to the BERKELEY.EDU realm, while sage.lcs.mit.edu would be mapped to the LCS.MIT.EDU realm.
LOGGING SECTION
The [logging] section indicates how a particular entity is to perform its logging. The relations specified in this section assign one or more values to the entity name.
Currently, the following entities are used:
- kdc
- These entries specify how the KDC is to perform its logging.
- admin_server
- These entries specify how the administrative server is to perform its logging.
- default
- These entries specify how to perform logging in the absence of explicit specifications otherwise.
Values are of the following forms:
- FILE=<filename>
- FILE:<filename>
- This value causes the entity's logging messages to go to the specified file. If the = form is used, then the file is overwritten. Otherwise, the file is appended to.
- STDERR
- This value causes the entity's logging messages to go to its standard error stream.
- CONSOLE
- This value causes the entity's logging messages to go to the console, if the system supports it.
- DEVICE=<devicename>
- This causes the entity's logging messages to go to the specified device.
- SYSLOG[:<severity>[:<facility>]]
-
This causes the entity's logging messages to go to the system log.
The severity argument specifies the default severity of system log messages. This may be any of the following severities supported by the syslog(3) call minus the LOG_ prefix: LOG_EMERG, LOG_ALERT, LOG_CRIT, LOG_ERR, LOG_WARNING, LOG_NOTICE, LOG_INFO, and LOG_DEBUG. For example, to specify LOG_CRIT severity, one would use CRIT for severity.
The facility argument specifies the facility under which the messages are logged. This may be any of the following facilities supported by the syslog(3) call minus the LOG_ prefix: LOG_KERN, LOG_USER, LOG_MAIL, LOG_DAEMON, LOG_AUTH, LOG_LPR, LOG_NEWS, LOG_UUCP, LOG_CRON, and LOG_LOCAL0 through LOG_LOCAL7.
If no severity is specified, the default is ERR, and if no facility is specified, the default is AUTH.
In the following example, the logging messages from the KDC will go to the console and to the system log under the facility LOG_DAEMON with default severity of LOG_INFO; and the logging messages from the administrative server will be appended to the file /var/adm/kadmin.log and sent to the device /dev/tty04.
[logging] kdc = CONSOLE kdc = SYSLOG:INFO:DAEMON admin_server = FILE:/var/adm/kadmin.log admin_server = DEVICE=/dev/tty04
CAPATHS SECTION
Cross-realm authentication is typically organized hierarchically. This hierarchy is based on the name of the realm, which thus imposes restrictions on the choice of realm names, and on who may participate in a cross-realm authentication. A non hierarchical orgization may be used, but requires a database to construct the authentication paths between the realms. This section defines that database.
A client will use this section to find the authentication path between its realm and the realm of the server. The server will use this section to verify the authentication path used be the client, by checking the transited field of the received ticket.
There is a tag name for each participating realm, and each tag has subtags for each of the realms. The value of the subtags is an intermediate realm which may participate in the cross-realm authentication. The subtags may be repeated if there is more then one intermediate realm. A value of "." means that the two realms share keys directly, and no intermediate realms should be allowed to participate.
There are n**2 possible entries in this table, but only those entries which will be needed on the client or the server need to be present. The client needs a tag for its local realm, with subtags for all the realms of servers it will need to authenticate with. A server needs a tag for each realm of the clients it will serve.
For example, ANL.GOV, PNL.GOV, and NERSC.GOV all wish to use the ES.NET realm as an intermediate realm. ANL has a sub realm of TEST.ANL.GOV which will authenticate with NERSC.GOV but not PNL.GOV. The [capath] section for ANL.GOV systems would look like this:
[capaths] ANL.GOV = { TEST.ANL.GOV = . PNL.GOV = ES.NET NERSC.GOV = ES.NET ES.NET = . } TEST.ANL.GOV = { ANL.GOV = . } PNL.GOV = { ANL.GOV = ES.NET } NERSC.GOV = { ANL.GOV = ES.NET } ES.NET = { ANL.GOV = . }
The [capath] section of the configuration file used on NERSC.GOV systems would look like this:
[capaths] NERSC.GOV = { ANL.GOV = ES.NET TEST.ANL.GOV = ES.NET TEST.ANL.GOV = ANL.GOV PNL.GOV = ES.NET ES.NET = . } ANL.GOV = { NERSC.GOV = ES.NET } PNL.GOV = { NERSC.GOV = ES.NET } ES.NET = { NERSC.GOV = . } TEST.ANL.GOV = { NERSC.GOV = ANL.GOV NERSC.GOV = ES.NET }
In the above examples, the ordering is not important, except when the same subtag name is used more then once. The client will use this to determing the path. (It is not important to the server, since the transited field is not sorted.)
If this section is not present, or if the client or server cannot find a client/server path, then normal hierarchical orginization is assumed.
This feature is not currently supported by DCE. DCE security servers can be used with Kerberized clients and servers, but versions prior to DCE 1.1 did not fill in the transited field, and should be used with caution.
DATABASE DEFAULT SECTION
The [dbdefaults] section indicates default values for the database specific parameters. It can also specify the configuration section under dbmodules for database specific parameters used by the loadable database library.
The following tags are used in this section:
- database_module
-
This relation indicates the name of the configuration section under dbmodules
for database specific parameters used by the loadable database library.
- database_name
-
This DB2-specific tag indicates the location of the database in the
filesystem.
- disable_last_success
-
If set to true, suppresses KDC updates to the "Last successful
authentication" field of principal entries requiring
preauthentication. Setting this flag may improve performance.
(Principal entries which do not require preauthentication never update
the "Last successful authentication" field.)
- disable_lockout
-
If set to true, suppresses KDC updates to the "Last failed
authentication" and "Failed password attempts" fields of principal
entries requiring preauthentication. Setting this flag may improve
performance, but also disables account lockout.
- ldap_kerberos_container_dn
-
This LDAP specific tag indicates the DN of the container object where the realm
objects will be located. This value is used if no object DN is mentioned in the
configuration section under dbmodules.
- ldap_kdc_dn
-
This LDAP specific tag indicates the default bind DN for the KDC server.
The KDC server does a login to the directory as this object. This value is used if
no object DN is mentioned in the configuration section under dbmodules.
- ldap_kadmind_dn
-
This LDAP specific tag indicates the default bind DN for the
Administration server. The Administration server does a login to the directory
as this object. This value is used if no object DN is mentioned in
the configuration section under dbmodules.
- ldap_service_password_file
-
This LDAP specific tag indicates the file containing the stashed passwords for the
objects used for starting the Kerberos servers. This value is used if no
service password file is mentioned in the configuration section under dbmodules.
- ldap_servers
-
This LDAP specific tag indicates the list of LDAP servers. The list of LDAP servers
is whitespace-separated. The LDAP server is specified by a LDAP URI.
This value is used if no LDAP servers are mentioned in the configuration
section under dbmodules.
- ldap_conns_per_server
-
This LDAP specific tag indicates the number of connections to be maintained per
LDAP server. This value is used if the number of connections per LDAP server are not
mentioned in the configuration section under dbmodules. The default value is 5.
DATABASE MODULE SECTION
Each tag in the [dbmodules] section of the file names a configuration section for database specific parameters that can be referred to by a realm. The value of the tag is a subsection where the relations in that subsection define the database specific parameters.
For each section, the following tags may be specified in the subsection:
- db_library
-
This tag indicates the name of the loadable database library.
The value should be db2 for db2 database and kldap for LDAP database.
- ldap_kerberos_container_dn
-
This LDAP specific tag indicates the DN of the container object where the realm
objects will be located.
- ldap_kdc_dn
-
This LDAP specific tag indicates the bind DN for the KDC server.
The KDC does a login to the directory as this object.
- ldap_kadmind_dn
-
This LDAP specific tag indicates the bind DN for the Administration server.
The Administration server does a login to the directory
as this object.
- ldap_service_password_file
-
This LDAP specific tag indicates the file containing the stashed passwords for the
objects used for starting the Kerberos servers.
- ldap_servers
-
This LDAP specific tag indicates the list of LDAP servers. The list of LDAP servers
is whitespace-separated. The LDAP server is specified by a LDAP URI.
- ldap_conns_per_server
-
This LDAP specific tag indicates the number of connections to be maintained per
LDAP server.
PLUGINS SECTION
Tags in the [plugins] section can be used to register dynamic plugin modules and to turn modules on and off. Not every krb5 pluggable interface uses the [plugins] section; the ones that do are documented here.
Each pluggable interface corresponds to a subsection of [plugins]. All subsections support the same tags:
- module
-
This tag may have multiple values. Each value is a string of the form
"modulename:pathname", which causes the shared object located at
pathname to be registered as a dynamic module named modulename for the
pluggable interface. If pathname is not an absolute path, it will be
treated as relative to the "krb5/plugins" subdirectory of the krb5
library directory.
- enable_only
-
This tag may have multiple values. If there are values for this tag,
then only the named modules will be enabled for the pluggable
interface.
- disable
-
This tag may have multiple values. If there are values for this tag,
then the named modules will be disabled for the pluggable interface.
The following subsections are currently supported within the [plugins] section:
pwqual interface
The pwqual subsection controls modules for the password quality interface, which is used to reject weak passwords when passwords are changed. In addition to any registered dynamic modules, the following built-in modules exist (and may be disabled with the disable tag):
- dict
-
Checks against the realm dictionary file
- empty
-
Rejects empty passwords
- hesiod
-
Checks against user information stored in Hesiod (only if Kerberos was
built with Hesiod support)
- princ
-
Checks against components of the principal name
kadm5_hook interface
The kadm5_hook interface provides plugins with information on principal creation, modification, password changes and deletion. This interface can be used to write a plugin to synchronize MIT Kerberos with another database such as Active Directory. No plugins are built in for this interface.
FILES
/etc/krb5.confSEE ALSO
syslog(3)
Index
- NAME
- DESCRIPTION
- LIBDEFAULTS SECTION
- APPDEFAULTS SECTION
- LOGIN SECTION
- REALMS SECTION
- DOMAIN_REALM SECTION
- LOGGING SECTION
- CAPATHS SECTION
- DATABASE DEFAULT SECTION
- DATABASE MODULE SECTION
- PLUGINS SECTION
- FILES
- SEE ALSO
This document was created by man2html, using the manual pages.
Time: 05:34:00 GMT, December 24, 2015


Play what you like.
Here is a little preview.
Chillwave
The perfect playlist to chill at the pool. 100% summer tracks.
Funky House
Time to party? Just click play and get ready for some good house music.
Deep & Tech
With deep & tech house, welcome to an underground world.
Mixtape
Not a dj? Don't worry, here is a selection of quality mixtapes for your party.


TI-73 Link Protocol Guide v1.0 - Packet formats
Texas Instruments calculators always send data and responses in
self-contained "packets."
Packets have the following format:
Note - all 2-byte integers are transmitted little-endian Intel-style
(least significant byte first).
| Offset | Length | Description |
|---|---|---|
| 0 | 1 byte | Machine ID byte |
| 1 | 1 byte | Command ID byte |
| 2 | 2 bytes | Length of data (see note below) |
| 4 | n bytes | Data (if attached) |
| 4+n | 2 bytes | Checksum (if data is attached) |
The Machine ID byte identifies the machine that is sending the packet. It can have one of the following values:
| Value | Description |
|---|---|
| 07h | Computer sending TI-73 data |
| 74h | TI-73 |
The Command ID byte identifies the request or response that the machine is sending. It can have one of the following values:
| Value | Description | Data Included |
|---|---|---|
| 06h | Variable Header (VAR) | A fixed-length, NUL padded variable header |
| 09h | Clear to send (CTS) | None |
| 15h | Data packet (DATA) | Screenshot/variable/backup data |
| 36h | Skip/Exit (SKIP/EXIT) | A one-byte rejection code (see codes below) |
| 56h | Acknowledge (ACK) | None |
| 5Ah | Checksum Error (ERR) The previous packet must be sent again. |
None |
| 68h | Check ready (RDY) | None |
| 6Dh | Silent - Request Screenshot (SCR) | None |
| 92h | End of Transmission (EOT) | None |
| A2h | Silent - Request Variable (REQ) | A fixed-length, NUL padded variable header |
| C9h | Silent - Request to Send Variable (RTS) | A fixed-length, NUL padded variable header |
Rejection codes (used with Command ID 36h) can have one of the following values:
| Value | Description |
|---|---|
| 01h | EXIT - The entire transmission has been cancelled. |
| 02h | SKIP - The current variable has been skipped. |
| 03h | OUT OF MEMORY (silent transmissions only) - The receiving calculator is out of memory. |
The checksum is a 16-bit value used to verify the integrity of the
data in the packet. It only present if data is present.
The checksum is calculated by taking the lower 16 bits of the sum of
the data bytes, as shown below:
int calculateChecksum(unsigned char* data, unsigned short datalength) {
unsigned short x, checksum;
for(x=0; x<datalength; x++) {
checksum+=data[x]; //overflow automatically limits to 16 bits
}
return checksum;
}
A Variable header contains information about one variable in the
calculator.
| Offset | Length | Description |
|---|---|---|
| 0 | 2 bytes | Size of actual variable data, in bytes |
| 2 | 1 byte | Type ID Byte (see type ID's below) |
| 3 | 8 bytes | Variable name, padded on the right with NULL characters (0h). This field is always tokenized. Not used for ID list. |
The type ID byte specifies the type of variable that is being transmitted. It can have one of the following values:
| Value | Description (click for variable format) |
|---|---|
| 00h | Real Number |
| 01h | Real List |
| 02h | Y-Variable |
| 05h | Program |
| 06h | Assembly Program ? |
| 07h | Picture |
| 0Bh | Window Settings (See note below) |
| 0Fh | Window Settings (See note below) |
| 11h | Table Setup (See note below) |
| 13h | Backup |
| 19h | Directory (See note below) - only used when requesting a directory |
| 23h | FLASH Operating System |
| 24h | FLASH Application |
| 26h | ID list |
| 27h | Get Certificate |
If the type ID byte specifies a backup, the variable header takes the following 9-byte format :
| Offset | Length | Description |
|---|---|---|
| 0 | 2 bytes | Size of first backup section (flags area), in bytes |
| 2 | 1 byte | Type ID Byte (13h in this case) |
| 3 | 2 bytes | Size of second backup section (data area), in bytes |
| 5 | 2 bytes | Size of third backup section (symbol area), in bytes |
| 7 | 2 bytes | Start User Area Address |
If the type ID byte is in the range 22...28h, the variable header takes the following 10-byte format :
| Offset | Length | Description |
|---|---|---|
| 0 | 2 bytes | Size of actual data, in bytes (LSB). |
| 2 | 1 byte | Type ID Byte (see type ID's below) |
| 3 | 2 bytes | Size of actual data, in bytes (MSB). |
| 5 | 1 byte | Flag - Always has a value of 0h but bit 7 is set if archived. |
| 6 | 2 bytes | FLASH offset |
| 8 | 2 bytes | FLASH page |


| My Hobbies |
Let me introduce myself. My name is Tatiana Voegerl. I was born in Regensburg, Germany to my mom, Amanda, and my dad, Christian. When I was really young, we moved to Coburg, Germany, which is where I grew up. In 2015, when I was 12, we moved to South Lyon, Michigan. I'm an only child, and my family consists of my mom, dad, and dog. I am in the South Lyon High School Marching Band as part of the Color Guard there, and I am part of the South Lyon Winter Guard as well. This past and upcoming season, I was a Section Leader of the Color Guard. Currently, I am a Senior at South Lyon High School. I am also part of our school's National Honor Society, and this year will be my second year participating. |
|---|---|
| Color Guard | My Aesthetic |
| Winter Guard | |
| Reading |
|
List of Countries I've Visited
|
My Favourite TV-Shows
|
|
||||||
|---|---|---|---|---|---|---|---|---|
|
|


leafy campus
Perma Links
CBSE
ICSE | ISC Syllabus
AACU
Login
Posted by
Admin
"Click for instructions"
News
Posted by
Admin
More News


I recently purchased about an ounce of dried mugwort from an herb shop. I had read about mugwort's potential as a dream potentiating herb, and it appealed to me more than calea zacatechichi (due to calea's side effects such as auditory and visionary hallucinations which, for probably a majority of those who are reading this would find that favorable, is not something I was looking for)
Anyway, I filled two capsules full of mugwort, and took each of the capsules within fifteen minutes. mugwort can supposedly produce a 'marijuana like high' but I did not experience this whatsoever, because 1)I have never tried marijuana and 2)I went to sleep shortly after I took the mugwort. I found a bit of difficulty in falling asleep, but I eventually did (perhaps the plant has some stimulant properties). In my sleep, I had many long and, for lack of a better way to describe them, epic dreams.
I managed to remember most of them, too. in the morning, as with most herbs, I did not feel any different at all, and I felt refreshed in a sense. mugwort is on some 'legal high' websites, but I personally would not recommend it for that. it can be smoked, but it is supposed to have a large tar level.
Experience Reports are the writings and opinions of the individual authors who submit them.
Some of the activities described are dangerous and/or illegal and none are recommended by Erowid.


Soon, a command centre for trash disposal
by Manoj SharmaThe Bruhat Bengaluru Mahanagara Palike (BBMP) is finalising plans to set up a command control centre for solid waste management.
The centre would prioritise and monitor the whole array of activities in solid waste management, right from door-to-door collection to transportation, quantitative analysis and categorisation of waste.
While tracking the auto tippers through maps connected to the Global Positioning System (GPS), the centre will send an alarm to the tipper if it overstays in an area, and indicate a breach in the procedure.
For their part, drivers of auto tippers should update the quantity and type of waste gathered from each household to help the BBMP understand the pattern and quantity of waste generated in a given area.
The command control area established in the BBMP head office would send messages to top-level officials as well as those deputed in the areas concerned to direct the contractor and pourakarmikas involved in door-to-door collection of garbage over specific issues.
Access to citizens
The centre would also allow the public to access garbage collection details such as waste collection timings in their area. Citizens can raise complaints with civic authorities in case of failures in the waste collection.
By setting up the system, the BBMP wants to determine the precise amount of waste produced in the city on a daily basis.
The existing system only allows the BBMP to find out waste generation from the number of trips compactors make to the landfill sites.
Looking to implement the plan under the Smart Cities Mission, the civic body has finalised the technical components and would come up with the cost estimation in a month’s time.
“We have finalised the technical components and will send the draft for approval,” S Sarfaraz Khan, joint commissioner for SWM, BBMP, told DH.
“We can study the process involved in waste management through the system and adopt suitable action, depending on the pattern. The system would reflect non-collection of waste from the house on contractors with a fine.”


Minderbot provides assistant-style interaction with the app.
Minderbot is in an extremely experimental state right now, and currently only responds to two commands:
Restart Minderbot


Namespace DevZest.Licensing
Classes
AssemblyInfo
Provides properties for getting the information about the assembly file, such as the version number, product information, public key xml, and so on.
AssemblyLicense
Represents the license that can be validated against the calling assembly.
AssemblyLicenseLoaderAttribute
Specifies the assembly license loader.
AssemblyLicenseProviderAttribute
Provides license from caller assembly.
CachedLicenseProviderAttribute
Provides cached license.
FileLicenseProviderAttribute
Provides license from local file system.
Freezable<T>
Represents object that can be frozen for modification.
IsolatedStorageFileLicenseProviderAttribute
Provides license from isolated storage file.
License
Provides the abstract base class for all licenses. A license is granted to an assembly signed with a strong name.
LicenseClient
Communicates with LicensePublisher to get published License.
LicenseError
Identifies the license validation error.
LicenseException
Represents the exception thrown when license validation failed.
LicenseItem
Represents a feature of License granted to an assembly.
LicenseItemAttribute
Declares license items of an assembly.
LicenseItemCollection
Represents a collection of LicenseItem objects.
LicenseManager
Provides static methods to get license from an assembly, determine if a valid license can be granted to an assembly, or reset license providers of an assembly.
LicenseProviderAttribute
Provides the abstract base class for all license providers.
LicensePublicKeyAttribute
Declares the public key used to verify the license.
LicensePublisher
Publishes signed licenses to LicenseClient.
LicensePublisherResponse
Represents the response sent from license publisher to license client.
MachineLicense
Represents the license that can be validated against the local machine.
RegistryLicenseProviderAttribute
Provides license from registry.
UserLicense
Represents the license that can be validated against the current user.
Structs
LicenseKey
Represents a license key that can be used to get License from LicensePublisher.
LicenseProviderResult
Represents the result of license providers, either a license XML string, or an error message string, plus an addition Data object.
Interfaces
IAssemblyLicenseLoader
Defines a method to load assembly license.
ILicensePublisher
Service contract between LicensePublisher and LicenseClient.
Enums
FolderOption
Specifies enumerated constants used to retrieve directory paths together with a file name.
LicenseErrorReason
Specifies the reason that fails the license validation.


Marksman Bixon:
For some reason, we have recently noticed an increase in numbers of grey keltir and black wolves near the village entrance...
By themselves, they are hardly a threat, but we are concerned that more dangerous predators will be drawn to the area as well. That is why we must hunt the grey keltir and black wolves now. Unfortunately, my time is taken up with other important tasks...
I hesitate to ask, but would you be willing to help me?
Agree to help.


A Trace-Based Performance Study of Autoscaling Workloads of Workflows in Datacenters
Traces used:
International Symposium on Cluster, Cloud and Grid Computing (CCGrid) 2018
Below we present publications by year that use one ore more traces of the Workflow Trace Archive.


Sum of the Distances to the Focal Points
One defining property of an ellipse is that, at any point on it, the sum of the distances to the two focal points is the same.
What is this sum also equal to? A clue is to look at the leftmost and rightmost points as, from there, the distance to each focal point can easily be expressed in terms of the semi-major axis a and the focal distance c.


You can categorize your questions by various interesting topics and afterwards you may even be able to look at how well others are doing, answering your questions.
A lot of users have posted questions into this quiz.
Test your skills against the multitude of different questions.
A lot of competitors test their skillset against the questions of M11's Quiz.
You can compare yourself and see how well you are faring.


Bachelors of Economics (July 2014)
Web Development 100 (2017)
I started college as in illustrator major, but during my second semester I decided to switch to Economics. Learning about what drives people to make decisions, whether financial or behavioral, fascinates me.
I grew up in Colombia and moved to New York City when I was 12 years old. I enjoy reading motivational books with coffee and porter beers. Drawing, playing with my dogs and skating by the Hudson River every summer afternoon are among my favorite acitvities.
Connecting with people and sharing ideas are of paramount importance to me. From showing my drawings, sharing books and articles I have read, sharing other people's experiences, or trying to ruin everybody's hypothetical ending of Game of Thrones, I am always up for a challenge.
I want to work with people that are deeply passionate about what they do; people that are willing to transcend the obvious choices in order to connect with the world.
I love visiting places that inspire me, as well as meet individuals that can motivate me. I love meeting people from different industries, learning what they do and how they approach their own challenges.
I've worked as a financial representative for a leading life insurance company, as a compliance analyst in an international banking firm and as a research assistant for a macroeconomic database. Currently, my interest lies on learning web development.


{{profile.name}}'s appointments!
Unconfirmed
Confirm
Confirmed
Project
{{a.client_project}}
Attendees
{{a.appointment.attendees}}
Summary
{{a.appointment.summary}}
Documents
Confirmed
{{a.confirmed_at}}
Add Appointment
Project:
Attendees:
Summary:
Documents:
save
cancel
Logout


Limitless - Color System
Overview
Custom colors system - a set of CSS classes that allow you to change colors on-the-fly directly in markup by changing class name. All colors correspond to Material design palette and includes 16 color palettes: 5 contextual (primary, danger, success, warning and info) and 11 alternative. The system is completely optional and moved to a separate colors.min.css
minified CSS file.
Basically color system is supported by almost all layout elements and components: sidebar, navbar, content panels, links, text, icons, alerts, dropdown menus, form components, tables, tabs, progress bars, buttons, notifications, popovers, tooltips etc. The system consists of 16 color palettes, each palette includes 1 main color and 5 alternate colors that are darker and lighter than the main one.
Available color palettes:
- Primary palette
- Danger palette
- Success palette
- Warning palette
- Info palette
- Pink palette
- Violet palette
- Purple palette
- Indigo palette
- Blue palette
- Teal palette
- Green palette
- Orange palette
- Brown palette
- Grey palette
- Slate palette
Basic usage
Usage is very simple, all you need to do is to add one of the color CSS classes to the element. Limitless template includes a bunch of pages with color palette usage demonstration - in components, elements and layout parts. Depending on what part of element you want to change, available classes are (primary
palette is an example):
| Class | Prefixes | Description |
|---|---|---|
| Background | ||
.bg-primary |
*-300, *-400, *-600, *-700, *-800 | Background color. Can be added to dropdown menus, sidebar, navbar, alerts, inputs, panels, selects etc. |
| Borders | ||
.border-primary |
*-300, *-400, *-600, *-700, *-800 | 4 sides border color. Any element that contains border |
border-top-primary |
Top border only. Any element that contains all sides border or top border only | |
border-bottom-primary |
Bottom border only. Any element that contains all sides border or bottom border only | |
border-left-primary |
Left border only. Any element that contains all sides border or left border only | |
border-right-primary |
Right border only. Any element that contains all sides border or right border only | |
| Text | ||
.text-primary |
*-300, *-400, *-600, *-700, *-800 | Text color. Can be used in text, icons and links |
| Alpha | ||
.alpha-primary |
none | Light background or text color. Useful when you need to use lighter color variations, in alerts for example |
Colors
Color system uses Material design palette colors with limitations: only 7 colors of 14 are used. I just tried to keep only main colors and drop unnecessary ones. Colored blocks below demonstrate all color codes and variables used in the template:
- 300 #64B5F6
- 400 #42A5F5
- 500 #2196F3
- 600 #1E88E5
- 700 #1976D2
- 800 #1565C0
- 300 #E57373
- 400 #EF5350
- 500 #F44336
- 600 #E53935
- 700 #D32F2F
- 800 #C62828
- 300 #81C784
- 400 #66BB6A
- 500 #4CAF50
- 600 #43A047
- 700 #388E3C
- 800 #2E7D32
- 300 #FF8A65
- 400 #FF7043
- 500 #FF5722
- 600 #F4511E
- 700 #E64A19
- 800 #D84315
- 300 #4DD0E1
- 400 #26C6DA
- 500 #00BCD4
- 600 #00ACC1
- 700 #0097A7
- 800 #00838F
- 300 #F06292
- 400 #EC407A
- 500 #E91E63
- 600 #D81B60
- 700 #C2185B
- 800 #AD1457
- 300 #BA68C8
- 400 #AB47BC
- 500 #9C27B0
- 600 #8E24AA
- 700 #7B1FA2
- 800 #6A1B9A
- 300 #9575CD
- 400 #7E57C2
- 500 #673AB7
- 600 #5E35B1
- 700 #512DA8
- 800 #4527A0
- 300 #7986CB
- 400 #5C6BC0
- 500 #3F51B5
- 600 #3949AB
- 700 #303F9F
- 800 #283593
- 300 #4FC3F7
- 400 #29B6F6
- 500 #03A9F4
- 600 #039BE5
- 700 #0288D1
- 800 #0277BD
- 300 #4DB6AC
- 400 #26A69A
- 500 #009688
- 600 #00897B
- 700 #00796B
- 800 #00695C
- 300 #AED581
- 400 #9CCC65
- 500 #8BC34A
- 600 #7CB342
- 700 #689F38
- 800 #558B2F
- 300 #FFB74D
- 400 #FFA726
- 500 #FF9800
- 600 #FB8C00
- 700 #F57C00
- 800 #EF6C00
- 300 #A1887F
- 400 #8D6E63
- 500 #795548
- 600 #6D4C41
- 700 #5D4037
- 800 #4E342E
- 300 #999
- 400 #888
- 500 #777
- 600 #666
- 700 #555
- 800 #444
- 300 #90A4AE
- 400 #78909C
- 500 #607D8B
- 600 #546E7A
- 700 #455A64
- 800 #37474F
LESS and CSS
Color system includes 2 source LESS files - colors.less
and palette.less
located in assets/less/core/colors/
folder. The first one includes class names and styles for them: background, borders, text and alpha colors. The second one includes list of all color variables.
Less folder root contains one more colors.less
file. This file is needed for colors.min.css
CSS file compile. Basically it includes paths to main LESS files, so when you compile CSS files, use this file:
// Core
// ------------------------------
// Import variables and mixins
@import "bootstrap/variables.less";
@import "bootstrap/mixins.less";
// Import overrides
@import "core/variables/variables.less";
@import "core/variables/core-variables.less";
// Color system, always load last
// ------------------------------
// Color palettes
@import "core/colors/palette.less";
// System itself
@import "core/colors/colors.less";
If you want to use color system in your project, i suggest to use minified colors.min.css
file included to the package, since basically this file won't be changed often, except if you may want to change colors in palette.less
file. But if you don't want to use the system, feel free to remove compiled CSS file, but don't remove any paths to palette.less
file in any LESS files, because color variables are used in different components and layout options.


in my school they are learner profiles. such as: inquirers. knowledgeable. thinkers. communicators. principled. open minded caring. courageous. balanced. reflective. leaader. steward. The organisation's name and logo were changed in 2007 to reflect new structural arrangements. Consequently, "IB" may now refer to the organisation itself, any of the four programmes, or the diploma or certificates awarded at the end of a programme. When Marie-Thérèse Maurette wrote "Educational Techniques for Peace. Do They Exist?" in 1948,[5] she created the framework for what would eventually become the IB Diploma Programme (IBDP). In the mid-1960s, a group of teachers from the International School of Geneva (Ecolint) created the International Schools Examinations Syndicate (ISES), which would later become the International Baccalaureate Office (IBO), followed by the International Baccalaureate Organisation (IBO) and then the International Baccalaureate (IB).
caring means: i am curious. i aks question. i like to learn. knowledgeable: i am smart. i know about the world near and far. thinkers: i apply my thinking skills critically and creatively to make good decisions and solve hard problems. communication. i share and receive ideas infomation in more than one way. principled i am honest ,fair,respectfull and responsible. open minded i appreciate my culture and views, values and traditions of other individuals and cultures.
Ib is an ackra name is International Baccalaureate The International Baccalaureate (IB), formerly known as the International Baccalaureate Organization (IBO), is a non-profit foundation headquartered in Geneva, Switzerland, and founded in 1968. It offers four educational programmes: the IB Diploma Programme and the IB Career-related Programme for students aged 15 to 19, the IB Middle Years Programme for students aged 11 to 16, and the IB Primary Years Programme for children aged 3 to 12. To teach these programmes, schools must be authorised by the International Baccalaureate.


--- layout: error-page title: Sorry... permalink: 500.html sitemap: false verb: "couldn't be processed" ---


The following is a list of compile dependencies for this project. These dependencies are required to compile and run the application:
| GroupId | ArtifactId | Version | Type |
|---|---|---|---|
| org.pojava | pojava | 2.6.1 | jar |
The following is a list of test dependencies for this project. These dependencies are only required to compile and run unit tests for the application:
| GroupId | ArtifactId | Version | Type |
|---|---|---|---|
| junit | junit | 3.8.2 | jar |
| mysql | mysql-connector-java | 5.1.10 | jar |
| postgresql | postgresql | 8.4-701.jdbc3 | jar |
No transitive dependencies are required for this project.
The GNU General Public License, Version 2: MySQL java connector
BSD License: PostgreSQL JDBC Driver
The Apache Software License, Version 2.0: POJava Persistence Utility, POJava Utilities
Common Public License Version 1.0: JUnit
| Filename | Size | Entries | Classes | Packages | JDK Rev | Debug |
|---|---|---|---|---|---|---|
| junit-3.8.2.jar | 117.81 kB | 120 | 102 | 6 | 1.2 | debug |
| mysql-connector-java-5.1.10.jar | 707.25 kB | 260 | 227 | 11 | 1.6 | debug |
| pojava-2.6.1.jar | 65.60 kB | 51 | 36 | 6 | 1.5 | debug |
| postgresql-8.4-701.jdbc3.jar | 461.75 kB | 219 | 194 | 20 | 1.4 | debug |
| Total | Size | Entries | Classes | Packages | JDK Rev | Debug |
| 4 | 1.32 MB | 650 | 559 | 43 | 1.6 | 4 |
| compile: 1 | compile: 65.60 kB | compile: 51 | compile: 36 | compile: 6 | - | compile: 1 |
| test: 3 | test: 1.26 MB | test: 599 | test: 523 | test: 37 | - | test: 3 |
| Repo ID | URL | Release | Snapshot |
|---|---|---|---|
| central | http://repo1.maven.org/maven2 | Yes | - |
Repository locations for each of the Dependencies.
| Artifact | central |
|---|---|
| junit:junit:jar:3.8.2 | |
| mysql:mysql-connector-java:jar:5.1.10 | |
| org.pojava:pojava:jar:2.6.1 | |
| postgresql:postgresql:jar:8.4-701.jdbc3 | |
| Total | central |
| 4 (compile: 1, test: 3) | 4 |


Toggle navigation
Home
Hi<EMAIL_ADDRESS>(Logout)
Let's eat together.
Friends
Holidays
Christmas
Super Bowl
Courses
Appetizers
Main Dishes
Side Dishes
Desserts
80% Complete (danger)
Appetizers
Main Dishes
Side Dishes
Desserts


Anferny Vanta
A sucker for progress and enlightenment
Pick up the phone
CONTACT MEA Person of Beauty
Don't give up on us baby
He can be kewl
He can play
He can graduate, ideally
He can smile
He can study
He can love
A sucker for progress and enlightenment
Pick up the phone
CONTACT MEDon't give up on us baby
He can be kewl
He can play
He can graduate, ideally
He can smile
He can study
He can love


1.) Return to main page and send a message
Notification should work
2.) Move this page side by side with the main page then send a message
Just like the image below:
(Notification should not work)


Serial chart can stack any graphs of the same kind. To achieve this set property of axis stackType to REGULAR in valueAxis.
axis
valueAxis


Toggle navigation
Debt Collector
Help
Loan Entry
$
.00
%
Payment
$0.00
Add
Clear
Loan List
Loan 1
Loan 2
Loan 3
Loan 4
Loan 5


--- layout: tweet ---
OH: #railsconf is like summer camp for programmers.
5/5/2016, 1:25:59 PM
Favs: 3
Retweets: 2


--- layout: post permalink: thecutekid.html Tags: Array NameOfCoupon: The Cute Kid Cash Back Summary: See our The Cute Kid Coupon Code, The Cute Kid Rebate, The Cute Kid Promo Code, The Cute Kid Discount, The Cute Kid Coupon Cash Back Rebate here. MetaKeywords: The Cute Kid Coupon Code, The Cute Kid Rebate, The Cute Kid Promo Code, The Cute Kid Cash Back Rebate, The Cute Kid Discount, The Cute Kid Coupon Image: images/14096.jpg LinkURL: http://www.shareasale.com/r.cfm?b=94526&u=412002&m=14096 affiliate_url_link: http://www.icouponblog.com/jane.php?id=1030 thesis_readmore: See the The Cute Kid Coupon thesis_thumb: http://www.icouponblog.com/tn.php?merchantURL=thecutekid.com Title: Save $6.00 - The Cute Kid Coupon Code for thecutekid.com. The Cute Kid Rebate & Discount thesis_description: Our The Cute Kid Discount Coupon Code for thecutekid.com. We have the best The Cute Kid Rebate anywhere. thesis_keywords: The Cute Kid, The Cute Kid Coupon Code, The Cute Kid Discount, The Cute Kid Rebate product_name: The Cute Kid hop_url: http://www.icouponblog.com/hop.php?id=1030 ---
If you have a real cute kid, you can submit their pictures to www.thecutekid.com. Let your child participate in an online photo contest. There is a big possibility that your child could be spotted by a talent agency and made a big star on television or in advertisements. Check out the website and see for yourself.
If you have the cutest kids or the cutest sets of twins, multiples, submit their photographs to www.thecutekid.com, your child might be the next super talent on television or an advertisement. Don’t limit your beautiful, cute kid to yourself. You may help him become a star. Visit www.thecutekid.com and discover for yourself. You will love www.thecutekid.com. Check it out today.


--- layout: post esbma_id: 1671 title: This Blog Entry is Urgent!!! date: 2007-05-24 18:21:48 keywords: laughs ---
SourceGear's mail room is where we keep the photocopier, fax machine and postage meter. It's also a storage place for office supplies, Kleenex, and the primary cause of most traffic into that room, candy.
A few minutes ago I walked over to the mail room to get a Kit Kat. On the fax machine I saw that we had received a page with the words "URGENT MEMO" in large letters across the top. Instantly I knew that it was a junk fax.
The word "urgent" isn't really all that useful anymore, because everybody who uses it is lying. In theory, the word "urgent" means "compelling immediate action or attention". Much to the dismay of my high school English teacher, most dictionaries today are regularly updated to be consistent with how words are typically used. How long before the dictionaries update the definition of "urgent" to reflect the most prevalent usage? If they did, one of the definitions of "urgent" would be "trivial, utterly useless, a complete waste of time".
As a writer, I find this terribly sad, but I see it so often that I'm numb. Every evening I go home and sort the junk mail that showed up in our mailbox that day. Although I do lament the way our language is being eroded away, I have to appreciate the steps they've taken to make my sorting job easier:
The shocking part of this story is that the people who send junk mail can't figure all this out. Take the word "urgent" off the outside of the envelope and I am far more likely to be deceived into thinking that it is actually urgent.
Perhaps I shouldn't be surprised. After all, anybody who tries to make their living using a fax machine to sell trips to Cancún is probably not the sharpest knife in the drawer.
Still, don't these people get junk mail everyday like the rest of us? Don't they get junk faxes and email spam?
Take this blog entry, for example. Here you are, over 400 words into it. Why did you come this far? You knew when you saw the title that I have absolutely nothing useful to say.


First virtual meetup.
New way of working
Corona virus outbracke significantly influenced our daily way of life. We should adapt to the new reality and new way of working.
We value all participants and health is the priority number one. So we decided to move all our metups to virtual meetups. I want to thay thank you to everyone who putted all effords to make in happen.
New schedule
Currently we will have a virtual meetup every Sunday, at 12am. We decided to keep working and move towards our goal: join Robocup@Work 2021.
Gazevo simulation
To make it happen we created the simulation environment in Gazebo, where you can already see the robot, lidar, stereo camera, odometry and IMU. It is all what we need to work on map generation and localization in real time. We currently working on improvement the simulation and will keep working on simulation of the arena of the Robocup arena.
Whant to try it out? See our repository for simulation.
Docker image for developers
We also addressed the problem of the varity of working enviriments on each feveloper machines. So we have a docker image that you can use to make sure you do not waste your time of setting up the ROS and all dependencies.
Chek it our and let us know if you need anything else. Docker image can be found here.
New Trello focus
We updated the trello board to reflect our new goals. We will focus on the saftware side and work on localization and simulation.
All previous activities will be paused and switched focus of our work on software part of the robot. We have enough tasks to keep everyone busy for next 2-3 months.
To check our current tasks, see our trello board.
Stay safe and see you soon!


It created a new schema in your server-side StackMob database named
testobject
.
View your new testobject schema
...and it also saved a
testobject
object - all in one call.
View the source, then learn more!
* All models and collections inherit from Backbone.js and hence share the same methods. Feel free to optionally learn more about Backbone!
If this message doesn't go away, something might be wrong. Don't forget to initialize the JS SDK!
Please run this in StackMob's Local Runner or through StackMob's GitHub-integrated hosting.


COMMING SOON
iCUE SP RGB PRO PERFORMANCE
LEARN MORE
M55 RGB PRO
MM300
HS70 WIRELESS SE
DOMINATOR PLATIUM RGB
Learn more about lastest product >
Learn more >
First time building a system? >


SMBPASSWD(5) File Formats and Conventions SMBPASSWD(5) NAME smbpasswd - The Samba encrypted password file SYNOPSIS smbpasswd DESCRIPTION This tool is part of the samba(7) suite. smbpasswd is the Samba encrypted password file. It contains the username, Unix user id and the SMB hashed passwords of the user, as well as account flag information and the time the password was last changed. This file format has been evolving with Samba and has had several different formats in the past. FILE FORMAT The format of the smbpasswd file used by Samba 2.2 is very similar to the familiar Unix passwd(5) file. It is an ASCII file containing one line for each user. Each field ithin each line is separated from the next by a colon. Any entry beginning with ´#´ is ignored. The smbpasswd file contains the following information for each user: name This is the user name. It must be a name that already exists in the standard UNIX passwd file. uid This is the UNIX uid. It must match the uid field for the same user entry in the standard UNIX passwd file. If this does not match then Samba will refuse to recognize this smbpasswd file entry as being valid for a user. Lanman Password Hash This is the LANMAN hash of the user´s password, encoded as 32 hex digits. The LANMAN hash is created by DES encrypting a well known string with the user´s password as the DES key. This is the same password used by Windows 95/98 machines. Note that this password hash is regarded as weak as it is vulnerable to dictionary attacks and if two users choose the same password this entry will be identical (i.e. the password is not "salted" as the UNIX password is). If the user has a null password this field will contain the characters "NO PASSWORD" as the start of the hex string. If the hex string is equal to 32 ´X´ characters then the user´s account is marked as disabled and the user will not be able to log onto the Samba server. WARNING !! Note that, due to the challenge-response nature of the SMB/CIFS authentication protocol, anyone with a knowledge of this password hash will be able to impersonate the user on the network. For this reason these hashes are known as plain text equivalents and must NOT be made available to anyone but the root user. To protect these passwords the smbpasswd file is placed in a directory with read and traverse access only to the root user and the smbpasswd file itself must be set to be read/write only by root, with no other access. NT Password Hash This is the Windows NT hash of the user´s password, encoded as 32 hex digits. The Windows NT hash is created by taking the user´s password as represented in 16-bit, little-endian UNICODE and then applying the MD4 (internet rfc1321) hashing algorithm to it. This password hash is considered more secure than the LANMAN Password Hash as it preserves the case of the password and uses a much higher quality hashing algorithm. However, it is still the case that if two users choose the same password this entry will be identical (i.e. the password is not "salted" as the UNIX password is). WARNING !!. Note that, due to the challenge-response nature of the SMB/CIFS authentication protocol, anyone with a knowledge of this password hash will be able to impersonate the user on the network. For this reason these hashes are known as plain text equivalents and must NOT be made available to anyone but the root user. To protect these passwords the smbpasswd file is placed in a directory with read and traverse access only to the root user and the smbpasswd file itself must be set to be read/write only by root, with no other access. Account Flags This section contains flags that describe the attributes of the users account. This field is bracketed by ´[´ and ´]´ characters and is always 13 characters in length (including the ´[´ and ´]´ characters). The contents of this field may be any of the following characters: · U - This means this is a "User" account, i.e. an ordinary user. · N - This means the account has no password (the passwords in the fields LANMAN Password Hash and NT Password Hash are ignored). Note that this will only allow users to log on with no password if the null passwords parameter is set in the smb.conf(5) config file. · D - This means the account is disabled and no SMB/CIFS logins will be allowed for this user. · X - This means the password does not expire. · W - This means this account is a "Workstation Trust" account. This kind of account is used in the Samba PDC code stream to allow Windows NT Workstations and Servers to join a Domain hosted by a Samba PDC. Other flags may be added as the code is extended in future. The rest of this field space is filled in with spaces. For further information regarding the flags that are supported please refer to the man page for the pdbedit command. Last Change Time This field consists of the time the account was last modified. It consists of the characters ´LCT-´ (standing for "Last Change Time") followed by a numeric encoding of the UNIX time in seconds since the epoch (1970) that the last change was made. All other colon separated fields are ignored at this time. VERSION This man page is correct for version 3 of the Samba suite. SEE ALSO smbpasswd(8), Samba(7), and the Internet RFC1321 for details on the MD4 algorithm. AUTHOR The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed. The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 was done by Alexander Bokovoy. Samba 3.6 06/22/2012 SMBPASSWD(5)


Class yii\sphinx\Command
| Inheritance | yii\sphinx\Command » yii\db\Command » yii\base\Component » yii\base\BaseObject |
|---|---|
| Implements | yii\base\Configurable |
| Available since version | 2.0 |
| Source Code | https://github.com/yiisoft/yii2-sphinx/blob/master/Command.php |
Command represents a SQL statement to be executed against a Sphinx.
A command object is usually created by calling yii\sphinx\Connection::createCommand(). The SQL statement it represents can be set via the $sql property.
To execute a non-query SQL (such as INSERT, REPLACE, DELETE, UPDATE), call execute(). To execute a SQL statement that returns result data set (such as SELECT, CALL SNIPPETS, CALL KEYWORDS), use queryAll(), queryOne(), queryColumn(), queryScalar(), or query(). For example,
$articles = $connection->createCommand("SELECT * FROM `idx_article` WHERE MATCH('programming')")->queryAll();
Command supports SQL statement preparation and parameter binding just as yii\db\Command does.
Command also supports building SQL statements by providing methods such as insert(), update(), etc. For example,
$connection->createCommand()->update('idx_article', [
'genre_id' => 15,
'author_id' => 157,
])->execute();
To build SELECT SQL statements, please use yii\sphinx\Query and yii\sphinx\QueryBuilder instead.
Public Properties
| Property | Type | Description | Defined By |
|---|---|---|---|
| $behaviors | yii\base\Behavior[] | List of behaviors attached to this component | yii\base\Component |
| $db | yii\sphinx\Connection | The Sphinx connection that this command is associated with. | yii\sphinx\Command |
| $fetchMode | integer | The default fetch mode for this command. | yii\db\Command |
| $params | array | The parameters (name => value) that are bound to the current PDO statement. | yii\db\Command |
| $pdoStatement | PDOStatement | The PDOStatement object that this command is associated with | yii\db\Command |
| $queryCacheDependency | yii\caching\Dependency | The dependency to be associated with the cached query result for this command | yii\db\Command |
| $queryCacheDuration | integer | The default number of seconds that query results can remain valid in cache. | yii\db\Command |
| $rawSql | string | The SQL statement to be set. | yii\db\Command |
| $sql | string | The SQL statement to be executed | yii\db\Command |
Public Methods
| Method | Description | Defined By |
|---|---|---|
| __call() | Calls the named method which is not a class method. | yii\base\Component |
| __clone() | This method is called after the object is created by cloning an existing one. | yii\base\Component |
| __construct() | Constructor. | yii\base\BaseObject |
| __get() | Returns the value of a component property. | yii\base\Component |
| __isset() | Checks if a property is set, i.e. defined and not null. | yii\base\Component |
| __set() | Sets the value of a component property. | yii\base\Component |
| __unset() | Sets a component property to be null. | yii\base\Component |
| addCheck() | Creates a SQL command for adding a check constraint to an existing table. | yii\db\Command |
| addColumn() | Creates a SQL command for adding a new DB column. | yii\sphinx\Command |
| addCommentOnColumn() | Builds a SQL command for adding comment to column. | yii\db\Command |
| addCommentOnTable() | Builds a SQL command for adding comment to table. | yii\db\Command |
| addDefaultValue() | Creates a SQL command for adding a default value constraint to an existing table. | yii\db\Command |
| addForeignKey() | Creates a SQL command for adding a foreign key constraint to an existing table. | yii\sphinx\Command |
| addPrimaryKey() | Creates a SQL command for adding a primary key constraint to an existing table. | yii\sphinx\Command |
| addUnique() | Creates a SQL command for adding an unique constraint to an existing table. | yii\db\Command |
| alterColumn() | Creates a SQL command for changing the definition of a column. | yii\sphinx\Command |
| attachBehavior() | Attaches a behavior to this component. | yii\base\Component |
| attachBehaviors() | Attaches a list of behaviors to the component. | yii\base\Component |
| batchInsert() | Creates a batch INSERT command. | yii\sphinx\Command |
| batchReplace() | Creates a batch REPLACE command. | yii\sphinx\Command |
| behaviors() | Returns a list of behaviors that this component should behave as. | yii\base\Component |
| bindParam() | Binds a parameter to the SQL statement to be executed. | yii\db\Command |
| bindValue() | Binds a value to a parameter. | yii\sphinx\Command |
| bindValues() | Binds a list of values to the corresponding parameters. | yii\sphinx\Command |
| cache() | Enables query cache for this command. | yii\db\Command |
| callKeywords() | Returns tokenized and normalized forms of the keywords, and, optionally, keyword statistics. | yii\sphinx\Command |
| callSnippets() | Builds a snippet from provided data and query, using specified index settings. | yii\sphinx\Command |
| canGetProperty() | Returns a value indicating whether a property can be read. | yii\base\Component |
| canSetProperty() | Returns a value indicating whether a property can be set. | yii\base\Component |
| cancel() | Cancels the execution of the SQL statement. | yii\db\Command |
| checkIntegrity() | Builds a SQL command for enabling or disabling integrity check. | yii\sphinx\Command |
| className() | Returns the fully qualified name of this class. | yii\base\BaseObject |
| createIndex() | Creates a SQL command for creating a new index. | yii\sphinx\Command |
| createTable() | Creates a SQL command for creating a new DB table. | yii\sphinx\Command |
| createView() | Creates a SQL View. | yii\db\Command |
| delete() | Creates a DELETE command. | yii\db\Command |
| detachBehavior() | Detaches a behavior from the component. | yii\base\Component |
| detachBehaviors() | Detaches all behaviors from the component. | yii\base\Component |
| dropCheck() | Creates a SQL command for dropping a check constraint. | yii\db\Command |
| dropColumn() | Creates a SQL command for dropping a DB column. | yii\sphinx\Command |
| dropCommentFromColumn() | Builds a SQL command for dropping comment from column. | yii\db\Command |
| dropCommentFromTable() | Builds a SQL command for dropping comment from table. | yii\db\Command |
| dropDefaultValue() | Creates a SQL command for dropping a default value constraint. | yii\db\Command |
| dropForeignKey() | Creates a SQL command for dropping a foreign key constraint. | yii\sphinx\Command |
| dropIndex() | Creates a SQL command for dropping an index. | yii\sphinx\Command |
| dropPrimaryKey() | Creates a SQL command for removing a primary key constraint to an existing table. | yii\sphinx\Command |
| dropTable() | Creates a SQL command for dropping a DB table. | yii\sphinx\Command |
| dropUnique() | Creates a SQL command for dropping an unique constraint. | yii\db\Command |
| dropView() | Drops a SQL View. | yii\db\Command |
| ensureBehaviors() | Makes sure that the behaviors declared in behaviors() are attached to this component. | yii\base\Component |
| execute() | Executes the SQL statement. | yii\db\Command |
| executeResetSequence() | Executes a db command resetting the sequence value of a table's primary key. | yii\db\Command |
| getBehavior() | Returns the named behavior object. | yii\base\Component |
| getBehaviors() | Returns all behaviors attached to this component. | yii\base\Component |
| getRawSql() | Returns the raw SQL by inserting parameter values into the corresponding placeholders in $sql. | yii\sphinx\Command |
| getSql() | Returns the SQL statement for this command. | yii\db\Command |
| hasEventHandlers() | Returns a value indicating whether there is any handler attached to the named event. | yii\base\Component |
| hasMethod() | Returns a value indicating whether a method is defined. | yii\base\Component |
| hasProperty() | Returns a value indicating whether a property is defined for this component. | yii\base\Component |
| init() | Initializes the object. | yii\base\BaseObject |
| insert() | Creates an INSERT command. | yii\db\Command |
| noCache() | Disables query cache for this command. | yii\db\Command |
| off() | Detaches an existing event handler from this component. | yii\base\Component |
| on() | Attaches an event handler to an event. | yii\base\Component |
| prepare() | Prepares the SQL statement to be executed. | yii\sphinx\Command |
| query() | Executes the SQL statement and returns query result. | yii\db\Command |
| queryAll() | Executes the SQL statement and returns ALL rows at once. | yii\db\Command |
| queryColumn() | Executes the SQL statement and returns the first column of the result. | yii\db\Command |
| queryOne() | Executes the SQL statement and returns the first row of the result. | yii\db\Command |
| queryScalar() | Executes the SQL statement and returns the value of the first column in the first row of data. | yii\db\Command |
| renameColumn() | Creates a SQL command for renaming a column. | yii\sphinx\Command |
| renameTable() | Creates a SQL command for renaming a DB table. | yii\sphinx\Command |
| replace() | Creates an REPLACE command. | yii\sphinx\Command |
| resetSequence() | Creates a SQL command for resetting the sequence value of a table's primary key. | yii\sphinx\Command |
| setRawSql() | Specifies the SQL statement to be executed. The SQL statement will not be modified in any way. | yii\db\Command |
| setSql() | Specifies the SQL statement to be executed. The SQL statement will be quoted using yii\db\Connection::quoteSql(). | yii\db\Command |
| trigger() | Triggers an event. | yii\base\Component |
| truncateIndex() | Creates a SQL command for truncating a runtime index. | yii\sphinx\Command |
| truncateTable() | Creates a SQL command for truncating a DB table. | yii\sphinx\Command |
| update() | Creates an UPDATE command. | yii\sphinx\Command |
| upsert() | Creates a command to insert rows into a database table if they do not already exist (matching unique constraints), or update them if they do. | yii\db\Command |
Protected Methods
| Method | Description | Defined By |
|---|---|---|
| bindPendingParams() | Binds pending parameters that were registered via bindValue() and bindValues(). | yii\db\Command |
| getCacheKey() | Returns the cache key for the query. | yii\db\Command |
| internalExecute() | Executes a prepared statement. | yii\db\Command |
| logQuery() | Logs the current database query if query logging is enabled and returns the profiling token if profiling is enabled. | yii\db\Command |
| queryInternal() | Performs the actual DB query of a SQL statement. | yii\db\Command |
| refreshTableSchema() | Refreshes table schema, which was marked by requireTableSchemaRefresh(). | yii\db\Command |
| requireTableSchemaRefresh() | Marks a specified table schema to be refreshed after command execution. | yii\db\Command |
| requireTransaction() | Marks the command to be executed in transaction. | yii\db\Command |
| reset() | Resets command properties to their initial state. | yii\db\Command |
| setRetryHandler() | Sets a callable (e.g. anonymous function) that is called when yii\db\Exception is thrown when executing the command. The signature of the callable should be: | yii\db\Command |
Property Details
The Sphinx connection that this command is associated with.
Method Details
Creates a SQL command for adding a new DB column.
| public $this addColumn ( $table, $column, $type ) | ||
| $table | string | The table that the new column will be added to. The table name will be properly quoted by the method. |
| $column | string | The name of the new column. The name will be properly quoted by the method. |
| $type | string | The column type. yii\db\QueryBuilder::getColumnType() will be called
to convert the give column type to the physical one. For example, |
| return | $this | The command object itself |
|---|
Creates a SQL command for adding a foreign key constraint to an existing table.
The method will properly quote the table and column names.
| public $this addForeignKey ( $name, $table, $columns, $refTable, $refColumns, $delete = null, $update = null ) | ||
| $name | string | The name of the foreign key constraint. |
| $table | string | The table that the foreign key constraint will be added to. |
| $columns | string|array | The name of the column to that the constraint will be added on. If there are multiple columns, separate them with commas. |
| $refTable | string | The table that the foreign key references to. |
| $refColumns | string|array | The name of the column that the foreign key references to. If there are multiple columns, separate them with commas. |
| $delete | string | The ON DELETE option. Most DBMS support these options: RESTRICT, CASCADE, NO ACTION, SET DEFAULT, SET NULL |
| $update | string | The ON UPDATE option. Most DBMS support these options: RESTRICT, CASCADE, NO ACTION, SET DEFAULT, SET NULL |
| return | $this | The command object itself |
|---|
Creates a SQL command for adding a primary key constraint to an existing table.
The method will properly quote the table and column names.
| public $this addPrimaryKey ( $name, $table, $columns ) | ||
| $name | string | The name of the primary key constraint. |
| $table | string | The table that the primary key constraint will be added to. |
| $columns | string|array | Comma separated string or array of columns that the primary key will consist of. |
| return | $this | The command object itself. |
|---|
Creates a SQL command for changing the definition of a column.
| public $this alterColumn ( $table, $column, $type ) | ||
| $table | string | The table whose column is to be changed. The table name will be properly quoted by the method. |
| $column | string | The name of the column to be changed. The name will be properly quoted by the method. |
| $type | string | The column type. yii\db\QueryBuilder::getColumnType() will be called
to convert the give column type to the physical one. For example, |
| return | $this | The command object itself |
|---|
Creates a batch INSERT command.
For example,
$connection->createCommand()->batchInsert('idx_user', ['name', 'age'], [
['Tom', 30],
['Jane', 20],
['Linda', 25],
])->execute();
Note that the values in each row must match the corresponding column names.
| public $this batchInsert ( $index, $columns, $rows ) | ||
| $index | string | The index that new rows will be inserted into. |
| $columns | array | The column names |
| $rows | array | The rows to be batch inserted into the index |
| return | $this | The command object itself |
|---|
Creates a batch REPLACE command.
For example,
$connection->createCommand()->batchReplace('idx_user', ['name', 'age'], [
['Tom', 30],
['Jane', 20],
['Linda', 25],
])->execute();
Note that the values in each row must match the corresponding column names.
| public $this batchReplace ( $index, $columns, $rows ) | ||
| $index | string | The index that new rows will be replaced. |
| $columns | array | The column names |
| $rows | array | The rows to be batch replaced in the index |
| return | $this | The command object itself |
|---|
Binds a value to a parameter.
| public $this bindValue ( $name, $value, $dataType = null ) | ||
| $name | string|integer | Parameter identifier. For a prepared statement
using named placeholders, this will be a parameter name of
the form |
| $value | mixed | The value to bind to the parameter |
| $dataType | integer | SQL data type of the parameter. If null, the type is determined by the PHP type of the value. |
| return | $this | The current command being executed |
|---|
Binds a list of values to the corresponding parameters.
This is similar to bindValue() except that it binds multiple values at a time. Note that the SQL data type of each value is determined by its PHP type.
| public $this bindValues ( $values ) | ||
| $values | array | The values to be bound. This must be given in terms of an associative
array with array keys being the parameter names, and array values the corresponding parameter values,
e.g. |
| return | $this | The current command being executed |
|---|
Returns tokenized and normalized forms of the keywords, and, optionally, keyword statistics.
| public $this callKeywords ( $index, $text, $fetchStatistic = false ) | ||
| $index | string | The name of the index from which to take the text processing settings |
| $text | string | The text to break down to keywords. |
| $fetchStatistic | boolean | Whether to return document and hit occurrence statistics |
| return | $this | The command object itself |
|---|
Builds a snippet from provided data and query, using specified index settings.
| public $this callSnippets ( $index, $source, $match, $options = [] ) | ||
| $index | string | Name of the index, from which to take the text processing settings. |
| $source | string|array | Is the source data to extract a snippet from. It could be either a single string or array of strings. |
| $match | string | The full-text query to build snippets for. |
| $options | array | List of options in format: optionName => optionValue |
| return | $this | The command object itself |
|---|
Builds a SQL command for enabling or disabling integrity check.
| public $this checkIntegrity ( $check = true, $schema = '', $table = '' ) | ||
| $check | boolean | Whether to turn on or off the integrity check. |
| $schema | string | The schema name of the tables. Defaults to empty string, meaning the current or default schema. |
| $table | string | The table name. |
| return | $this | The command object itself |
|---|---|---|
| throws | yii\base\NotSupportedException | if this is not supported by the underlying DBMS |
Creates a SQL command for creating a new index.
| public $this createIndex ( $name, $table, $columns, $unique = false ) | ||
| $name | string | The name of the index. The name will be properly quoted by the method. |
| $table | string | The table that the new index will be created for. The table name will be properly quoted by the method. |
| $columns | string|array | The column(s) that should be included in the index. If there are multiple columns, please separate them by commas. The column names will be properly quoted by the method. |
| $unique | boolean | Whether to add UNIQUE constraint on the created index. |
| return | $this | The command object itself |
|---|
Creates a SQL command for creating a new DB table.
The columns in the new table should be specified as name-definition pairs (e.g. 'name' => 'string'),
where name stands for a column name which will be properly quoted by the method, and definition
stands for the column type which can contain an abstract DB type.
The method yii\sphinx\QueryBuilder::getColumnType() will be called
to convert the abstract column types to physical ones. For example, string
will be converted
as varchar(255)
, and string not null
becomes varchar(255) not null
.
If a column is specified with definition only (e.g. 'PRIMARY KEY (name, type)'), it will be directly inserted into the generated SQL.
| public $this createTable ( $table, $columns, $options = null ) | ||
| $table | string | The name of the table to be created. The name will be properly quoted by the method. |
| $columns | array | The columns (name => definition) in the new table. |
| $options | string | Additional SQL fragment that will be appended to the generated SQL. |
| return | $this | The command object itself |
|---|
Creates a SQL command for dropping a DB column.
| public $this dropColumn ( $table, $column ) | ||
| $table | string | The table whose column is to be dropped. The name will be properly quoted by the method. |
| $column | string | The name of the column to be dropped. The name will be properly quoted by the method. |
| return | $this | The command object itself |
|---|
Creates a SQL command for dropping a foreign key constraint.
| public $this dropForeignKey ( $name, $table ) | ||
| $name | string | The name of the foreign key constraint to be dropped. The name will be properly quoted by the method. |
| $table | string | The table whose foreign is to be dropped. The name will be properly quoted by the method. |
| return | $this | The command object itself |
|---|
Creates a SQL command for dropping an index.
| public $this dropIndex ( $name, $table ) | ||
| $name | string | The name of the index to be dropped. The name will be properly quoted by the method. |
| $table | string | The table whose index is to be dropped. The name will be properly quoted by the method. |
| return | $this | The command object itself |
|---|
Creates a SQL command for removing a primary key constraint to an existing table.
| public $this dropPrimaryKey ( $name, $table ) | ||
| $name | string | The name of the primary key constraint to be removed. |
| $table | string | The table that the primary key constraint will be removed from. |
| return | $this | The command object itself |
|---|
Creates a SQL command for dropping a DB table.
| public $this dropTable ( $table ) | ||
| $table | string | The table to be dropped. The name will be properly quoted by the method. |
| return | $this | The command object itself |
|---|
Returns the raw SQL by inserting parameter values into the corresponding placeholders in $sql.
Note that the return value of this method should mainly be used for logging purpose. It is likely that this method returns an invalid SQL due to improper replacement of parameter placeholders.
| public string getRawSql ( ) | ||
| return | string | The raw SQL with parameter values inserted into the corresponding placeholders in $sql. |
|---|
Prepares the SQL statement to be executed.
For complex SQL statement that is to be executed multiple times, this may improve performance. For SQL statement with binding parameters, this method is invoked automatically.
| public void prepare ( $forRead = null ) | ||
| $forRead | boolean | Whether this method is called for a read query. If null, it means the SQL statement should be used to determine whether it is for read or write. |
| throws | yii\db\Exception | if there is any DB error |
|---|
Creates a SQL command for renaming a column.
| public $this renameColumn ( $table, $oldName, $newName ) | ||
| $table | string | The table whose column is to be renamed. The name will be properly quoted by the method. |
| $oldName | string | The old name of the column. The name will be properly quoted by the method. |
| $newName | string | The new name of the column. The name will be properly quoted by the method. |
| return | $this | The command object itself |
|---|
Creates a SQL command for renaming a DB table.
| public $this renameTable ( $table, $newName ) | ||
| $table | string | The table to be renamed. The name will be properly quoted by the method. |
| $newName | string | The new table name. The name will be properly quoted by the method. |
| return | $this | The command object itself |
|---|
Creates an REPLACE command.
For example,
$connection->createCommand()->replace('idx_user', [
'name' => 'Sam',
'age' => 30,
])->execute();
The method will properly escape the column names, and bind the values to be replaced.
Note that the created command is not executed until execute() is called.
| public $this replace ( $index, $columns ) | ||
| $index | string | The index that new rows will be replaced into. |
| $columns | array | The column data (name => value) to be replaced into the index. |
| return | $this | The command object itself |
|---|
Creates a SQL command for resetting the sequence value of a table's primary key.
The sequence will be reset such that the primary key of the next new row inserted will have the specified value or the maximum existing value +1.
| public $this resetSequence ( $table, $value = null ) | ||
| $table | string | The name of the table whose primary key sequence will be reset |
| $value | mixed | The value for the primary key of the next new row inserted. If this is not set, the next new row's primary key will have the maximum existing value +1. |
| return | $this | The command object itself |
|---|---|---|
| throws | yii\base\NotSupportedException | if this is not supported by the underlying DBMS |
Creates a SQL command for truncating a runtime index.
| public $this truncateIndex ( $index ) | ||
| $index | string | The index to be truncated. The name will be properly quoted by the method. |
| return | $this | The command object itself |
|---|
Creates a SQL command for truncating a DB table.
| public $this truncateTable ( $table ) | ||
| $table | string | The table to be truncated. The name will be properly quoted by the method. |
| return | $this | The command object itself |
|---|
Creates an UPDATE command.
For example,
$connection->createCommand()->update('user', ['status' => 1], 'age > 30')->execute();
The method will properly escape the column names and bind the values to be updated.
Note that the created command is not executed until execute() is called.
| public $this update ( $index, $columns, $condition = '', $params = [], $options = [] ) | ||
| $index | string | The index to be updated. |
| $columns | array | The column data (name => value) to be updated. |
| $condition | string|array | The condition that will be put in the WHERE part. Please refer to yii\sphinx\Query::where() on how to specify condition. |
| $params | array | The parameters to be bound to the command |
| $options | array | List of options in format: optionName => optionValue |
| return | $this | The command object itself |
|---|


Apache Flink 1.14.4 Release Announcement
March 11, 2022 - Konstantin Knauf (@snntrable)The Apache Flink Community is pleased to announce another bug fix release for Flink 1.14.
This release includes 51 bug and vulnerability fixes and minor improvements for Flink 1.14. Below you will find a list of all bugfixes and improvements (excluding improvements to the build infrastructure and build stability). For a complete list of all changes see: JIRA.
We highly recommend all users to upgrade to Flink 1.14.4.
Release Artifacts #
Maven Dependencies #
<dependency>
<groupId>org.apache.flink</groupId>
<artifactId>flink-java</artifactId>
<version>1.14.4</version>
</dependency>
<dependency>
<groupId>org.apache.flink</groupId>
<artifactId>flink-streaming-java_2.11</artifactId>
<version>1.14.4</version>
</dependency>
<dependency>
<groupId>org.apache.flink</groupId>
<artifactId>flink-clients_2.11</artifactId>
<version>1.14.4</version>
</dependency>
Binaries #
You can find the binaries on the updated Downloads page.
Docker Images #
- library/flink (official images)
- apache/flink (ASF repository)
PyPi #
Release Notes #
Sub-task
- [FLINK-21788] - Throw PartitionNotFoundException if the partition file has been lost for blocking shuffle
- [FLINK-24954] - Reset read buffer request timeout on buffer recycling for sort-shuffle
- [FLINK-25653] - Move buffer recycle in SortMergeSubpartitionReader out of lock to avoid deadlock
- [FLINK-25654] - Remove the redundant lock in SortMergeResultPartition
- [FLINK-25879] - Track used search terms in Matomo
- [FLINK-25880] - Implement Matomo in Flink documentation
Bug
- [FLINK-21752] - NullPointerException on restore in PojoSerializer
- [FLINK-23946] - Application mode fails fatally when being shut down
- [FLINK-24334] - Configuration kubernetes.flink.log.dir not working
- [FLINK-24407] - Pulsar connector chinese document link to Pulsar document location incorrectly.
- [FLINK-24607] - SourceCoordinator may miss to close SplitEnumerator when failover frequently
- [FLINK-25171] - When the DDL statement was executed, the column names of the Derived Columns were not validated
- [FLINK-25199] - StreamEdges are not unique in self-union, which blocks propagation of watermarks
- [FLINK-25362] - Incorrect dependencies in Table Confluent/Avro docs
- [FLINK-25407] - Network stack deadlock when cancellation happens during initialisation
- [FLINK-25466] - TTL configuration could parse in StateTtlConfig#DISABLED
- [FLINK-25486] - Perjob can not recover from checkpoint when zookeeper leader changes
- [FLINK-25494] - Duplicate element serializer during DefaultOperatorStateBackendSnapshotStrategy#syncPrepareResources
- [FLINK-25678] - TaskExecutorStateChangelogStoragesManager.shutdown is not thread-safe
- [FLINK-25683] - wrong result if table transfrom to DataStream then window process in batch mode
- [FLINK-25728] - Potential memory leaks in StreamMultipleInputProcessor
- [FLINK-25732] - Dispatcher#requestMultipleJobDetails returns non-serialiable collection
- [FLINK-25827] - Potential memory leaks in SourceOperator
- [FLINK-25856] - Fix use of UserDefinedType in from_elements
- [FLINK-25883] - The value of DEFAULT_BUNDLE_PROCESSOR_CACHE_SHUTDOWN_THRESHOLD_S is too large
- [FLINK-25893] - ResourceManagerServiceImpl's lifecycle can lead to exceptions
- [FLINK-25952] - Savepoint on S3 are not relocatable even if entropy injection is not enabled
- [FLINK-26039] - Incorrect value getter in map unnest table function
- [FLINK-26159] - Pulsar Connector: should add description MAX_FETCH_RECORD in doc to explain slow consumption
- [FLINK-26160] - Pulsar Connector: stopCursor description should be changed. Connector only stop when auto discovery is disabled.
- [FLINK-26187] - Chinese docs override english aliases
- [FLINK-26304] - GlobalCommitter can receive failed committables
New Feature
- [FLINK-20188] - Add Documentation for new File Source
- [FLINK-21407] - Clarify which sources and APIs support which formats
Improvement
- [FLINK-20830] - Add a type of HEADLESS_CLUSTER_IP for rest service type
- [FLINK-24880] - Error messages "OverflowError: timeout value is too large" shown when executing PyFlink jobs
- [FLINK-25160] - Make doc clear: tolerable-failed-checkpoints counts consecutive failures
- [FLINK-25611] - Remove CoordinatorExecutorThreadFactory thread creation guards
- [FLINK-25650] - Document unaligned checkpoints performance limitations (larger records/flat map/timers/...)
- [FLINK-25767] - Translation of page 'Working with State' is incomplete
- [FLINK-25818] - Add explanation how Kafka Source deals with idleness when parallelism is higher then the number of partitions
Technical Debt
- [FLINK-25576] - Update com.h2database:h2 to 2.0.206
- [FLINK-25785] - Update com.h2database:h2 to 2.0.210


Google Fi effectively discounts Pixel 4 by 50% with service credit deal
by Abner LiIn addition to the Google Store kicking off Black Friday deals on Pixel 4 and Pixel Slate today, Google Fi’s “holiday savings” are now underway. Instead of a straight discount, the MVNO has an interesting offer that essentially discounts the Made by Google flagships by 50%.
With any Pixel 4 purchase, get 50% of what you pay today back in Fi service credit (up to $500), with minimum of 60 day activation.
This promotion sees you pay full price for the Pixel 4 or Pixel 4 XL today, but you get back a significant amount in service credit that goes towards your monthly bill. This effectively discounts the phone in half as you won’t have to pay your cellular plan for the first few months.
- $799 Pixel 4 64 GB — $400 Fi Credit
- $899 Pixel 4 128 GB — $450 Fi Credit
- $899 Pixel 4 XL 64 GB — $450 Fi Credit
- $999 Pixel 4 XL 128 GB — $500 Fi Credit
That said, the credit will not be delivered immediately and requires that certain conditions be met. Open to new and existing customers, you have to remain active on Fi for 60 consecutive days.
You will receive an email notification after all terms and conditions have been satisfied, and the credit will be applied to your subsequent bills (usually 60-90 days after activation).
Last month with the Pixel 4’s launch, Fi pre-orderers received a $100 service credit. Like the Google Store, this will likely cause a furor among early adopters. All storage and color configurations — except the Oh So Orange Pixel 4 XL — are currently available. The Fi Pixel 4 50% discount starts today and ends on December 2nd.
Those that want an instant discount can get $200 off all Pixel 4 models from the Google Store. Meanwhile, Fi has the Pixel 3a at $249 and Pixel 3a XL at $329. The discounted price will automatically be applied during checkout.
More about Google Fi:
- Google Fi courting travelers by selling SIM cards in airport vending machines
- RCS Messaging and DSDS support comes to Pixel 4 on Google Fi
- Google Fi SIM cards are now available at Target
FTC: We use income earning auto affiliate links. More.