Sponsored Content
The Lounge What is on Your Mind? Resolved: Issue in Server Data Center Post 303029633 by Neo on Wednesday 30th of January 2019 01:26:29 AM
Old 01-30-2019
FYI:

Image
 

6 More Discussions You Might Find Interesting

1. HP-UX

Need to set up a HP cluster system in a data center

What are the server requirements, Software requirements, Network requirements etc, Please help me.. as 'm new 'm unable to get things done @ my end alone. Please refrain from typing subjects completely in upper case letters to get more attention, ty. (5 Replies)
Discussion started by: Sounddappan
5 Replies

2. Infrastructure Monitoring

Agent Installation Issue on Ops Center

Hi guys . While installing the agent on an asset Solaris system: root@system: /var/tmp/OC $ /opt/SUNWxvmoc/bin/agentadm configure -u root -p /var/tmp/OC/mypasswd -x 172.21.16.65 agentadm: Version 12.1.2.2161 launched with args: configure -u root -p /var/tmp/OC/mypasswd -x 172.21.16.65 Validating... (3 Replies)
Discussion started by: Junaid Subhani
3 Replies

3. Solaris

[Resolved] Strange Issue with user logins

Ok got a strange one here. None of my user accounts are able to login into the system. When trying to ssh to the server i get the following. Could not chdir to home directory /home/<homedir>: Permission denied /bin/sh: Permission denied I checked the permissions on the home directory and even... (7 Replies)
Discussion started by: JoeDirte
7 Replies

4. Shell Programming and Scripting

Failure rate of a node / Data center

Hi, Please, i have a history of the state of each node in my data center. an history about the failure of my cluster (UN: node up, DN: node down). Here is some lines of the history: 08:51:36 UN 127.0.0.1 08:51:36 UN 127.0.0.2 08:51:36 UN 127.0.0.3 08:53:50 DN 127.0.0.1 ... (6 Replies)
Discussion started by: chercheur111
6 Replies

5. What is on Your Mind?

Cut Over to New Data Center and Upgraded OS Done. :)

Three days ago we received an expected notice from our long time data center that they were going dark on Sept 12th. About one and a half hours ago, after three days of marathon work, I just cut over the unix.com to a new data center with a completely new OS and Ubuntu distribution. (22 Replies)
Discussion started by: Neo
22 Replies

6. What is on Your Mind?

OUTAGE: Data Center Problem Resolved.

There was a problem with our data center today, creating a site outage (server unreachable). That problem has been resolved. Basically, it seems to have been a socially engineered denial-of-service attack against UNIX.com; which I stopped as soon as I found out what the problem was. Total... (2 Replies)
Discussion started by: Neo
2 Replies
HTML::Lint(3pm) 					User Contributed Perl Documentation					   HTML::Lint(3pm)

NAME
HTML::Lint - check for HTML errors in a string or file VERSION
Version 2.20 SYNOPSIS
my $lint = HTML::Lint->new; $lint->only_types( HTML::Lint::Error::STRUCTURE ); $lint->parse( $data ); $lint->parse_file( $filename ); my $error_count = $lint->errors; foreach my $error ( $lint->errors ) { print $error->as_string, " "; } HTML::Lint also comes with a wrapper program called weblint that handles linting from the command line: $ weblint http://www.cnn.com/ http://www.cnn.com/ (395:83) <IMG SRC="spacer.gif"> tag has no HEIGHT and WIDTH attributes. http://www.cnn.com/ (395:83) <IMG SRC="goofus.gif"> does not have ALT text defined http://www.cnn.com/ (396:217) Unknown element <nobr> http://www.cnn.com/ (396:241) </nobr> with no opening <nobr> http://www.cnn.com/ (842:7) target attribute in <a> is repeated And finally, you can also get Apache::HTML::Lint that passes any mod_perl-generated code through HTML::Lint and get it dumped into your Apache error_log. [Mon Jun 3 14:03:31 2002] [warn] /foo.pl (1:45) </p> with no opening <p> [Mon Jun 3 14:03:31 2002] [warn] /foo.pl (1:49) Unknown element <gronk> [Mon Jun 3 14:03:31 2002] [warn] /foo.pl (1:56) Unknown attribute "x" for tag <table> METHODS
NOTE: Some of these methods mirror HTML::Parser's methods, but HTML::Lint is not a subclass of HTML::Parser. new() Create an HTML::Lint object, which inherits from HTML::Parser. You may pass the types of errors you want to check for in the "only_types" parm. my $lint = HTML::Lint->new( only_types => HTML::Lint::Error::STRUCTURE ); If you want more than one, you must pass an arrayref: my $lint = HTML::Lint->new( only_types => [HTML::Lint::Error::STRUCTURE, HTML::Lint::Error::FLUFF] ); $lint->parser() Returns the parser object for this object, creating one if necessary. $lint->parse( $text ) $lint->parse( $code_ref ) Passes in a chunk of HTML to be linted, either as a piece of text, or a code reference. See HTML::Parser's "parse_file" method for details. $lint->parse_file( $file ) Analyzes HTML directly from a file. The $file argument can be a filename, an open file handle, or a reference to an open file handle. See HTML::Parser's "parse_file" method for details. $lint->eof Signals the end of a block of text getting passed in. This must be called to make sure that all parsing is complete before looking at errors. Any parameters (and there shouldn't be any) are passed through to HTML::Parser's eof() method. $lint->errors() In list context, "errors" returns all of the errors found in the parsed text. Each error is an object of the type HTML::Lint::Error. In scalar context, it returns the number of errors found. $lint->clear_errors() Clears the list of errors, in case you want to print and clear, print and clear. $lint->only_types( $type1[, $type2...] ) Specifies to only want errors of a certain type. $lint->only_types( HTML::Lint::Error::STRUCTURE ); Calling this without parameters makes the object return all possible errors. The error types are "STRUCTURE", "HELPER" and "FLUFF". See HTML::Lint::Error for details on these types. $lint->gripe( $errcode, [$key1=>$val1, ...] ) Adds an error message, in the form of an HTML::Lint::Error object, to the list of error messages for the current object. The file, line and column are automatically passed to the HTML::Lint::Error constructor, as well as whatever other key value pairs are passed. For example: $lint->gripe( 'attr-repeated', tag => $tag, attr => $attr ); Usually, the user of the object won't call this directly, but just in case, here you go. $lint->newfile( $filename ) Call "newfile()" whenever you switch to another file in a batch of linting. Otherwise, the object thinks everything is from the same file. Note that the list of errors is NOT cleared. Note that $filename does NOT need to match what's put into parse() or parse_file(). It can be a description, a URL, or whatever. MODIFYING HTML
::LINT'S BEHAVIOR Sometimes you'll have HTML that for some reason cannot conform to HTML::Lint's expectations. For those instances, you can use HTML comments to modify HTML::Lint's behavior. Say you have an image where for whatever reason you can't get dimensions for the image. This HTML snippet: <img src="logo.png" height="120" width="50" alt="Company logo"> <img src="that.png"> causes this error: foo.html (14:20) <img src="that.png"> tag has no HEIGHT and WIDTH attributes But if for some reason you can't get those dimensions when you build the page, you can at least stop HTML::Lint complaining about it. <img src="this.png" height="120" width="50" alt="Company logo"> <!-- html-lint elem-img-sizes-missing: off, elem-img-alt-missing: off --> <img src="that.png"> <!-- html-lint elem-img-sizes-missing: on, elem-img-alt-missing: off --> If you want to turn off all HTML::Lint warnings for a block of code, use <!-- html-lint all: off --> And turn them back on with <!-- html-lint all: off --> You don't have to use "on" and "off". For "on", you can use "true" or "1". For "off", you can use "0" or "false". For a list of possible errors and their codes, see HTML::Lint::Error, or run perldoc HTML::Lint::Error. BUGS, WISHES AND CORRESPONDENCE All bugs and requests are now being handled through GitHub. https://github.com/petdance/html-lint/issues DO NOT send bug reports to http://rt.cpan.org/ or http://code.google.com/ TODO
o Check for attributes that require values o <TABLE>s that have no rows. o Form fields that aren't in a FORM o Check for valid entities, and that they end with semicolons o DIVs with nothing in them. o HEIGHT= that have percents in them. o Check for goofy stuff like: <b><li></b><b>Hello Reader - Spanish Level 1 (K-3)</b> COPYRIGHT &; LICENSE Copyright 2005-2012 Andy Lester. This program is free software; you can redistribute it and/or modify it under the terms of the Artistic License v2.0. http://www.opensource.org/licenses/Artistic-2.0 Please note that these modules are not products of or supported by the employers of the various contributors to the code. AUTHOR
Andy Lester, andy at petdance.com perl v5.14.2 2012-04-06 HTML::Lint(3pm)
All times are GMT -4. The time now is 05:46 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy