06-21-2002
??? Nice? Bent out of shape? Sorry, you must be reading something into it. A reminder yes. Only to allow the person to learn the different support out there.
fyi - no vendor support is needed for the web site that I know of - I didn't use any sign in or contract number for the knowledge base - Legato is pretty good as far as that (the software isn't but the web page is)
Also note I request that the person do the search themselves - because more than one answer comes back - I put only the first one...they must go there as Legato does have many particulars about it that could cause the problem.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi all
what may be the cause when i try to restore the backup (TAR)
It's giving error
tar block size =1
directory checksum error
please suggest as soon as possible
try n learn
praful (4 Replies)
Discussion started by: Prafulla
4 Replies
2. UNIX for Advanced & Expert Users
I am running my solstice backup 5.5.1 server on a solaris 2.6 platform.
I have a remote client ; my mailserver also running solaris 2.6.
I created a unique pool and group for my mailserver, but when i label to pool, mount and run backup, it doesnt backup my mailserver, rather it gives me error... (10 Replies)
Discussion started by: lealyz
10 Replies
3. UNIX for Dummies Questions & Answers
Hi. Can someone please tell what the following tape error message means:
Read end of medium on output
If you want to go on, type device/file name when ready
This message comes after the terminal displays a few files from the directory I'm trying to backup.
The command I'm running is:
... (1 Reply)
Discussion started by: cstovall
1 Replies
4. UNIX for Dummies Questions & Answers
We have an older HP Unix 10.20 system that we rarely ever use anymore. Most of our jobs on it are from 1994 to 2002. Anything after that is on Windows XP. The Unix system was backed up religiously every day. Because of space constraints some of the jobs were removed from the system after a... (3 Replies)
Discussion started by: fozzybear
3 Replies
5. UNIX and Linux Applications
Hi! This is my first post and im not that familiar with UNIX but I'll try to explain my problem..
I have a server here at work running Open UNIX Release 8.0.0
It has a special application on it that I'm trying to run a database backup on. For the last 2 weeks this has failed.. Usually the... (2 Replies)
Discussion started by: TaZ
2 Replies
6. Shell Programming and Scripting
Hi,
Following is the script I made for backing up Cpanel server.
================================================
#! /bin/bash
rsync -raopguzl --delete --exclude "*.tar.gz" --progress --delete-excluded root@$hostname:/$otherdir/$i/ /mnt/iscsi/$hostname/home/$i
done
... (6 Replies)
Discussion started by: mohitmoudgil
6 Replies
7. Shell Programming and Scripting
I have script but not work..
=====================================
#!/bin/bash
# backup
Backup_Dirs="/home/test"
Backup_Dest_Dir=/tmp
Backup_Date=`date +%b%d%y`
#Create Backup
tar cvzf $Backup_Date.tar.gz $Backup_Dirs $Backup_Dest_Dir
======================================
What's... (1 Reply)
Discussion started by: mbah_jiman
1 Replies
8. Ubuntu
Hi I am using Ubuntu back up program to the back up automatic.
Problem is that recently the app start to fail.
I get the following message:
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1359, in <module>
with_tempdir(main)
File "/usr/bin/duplicity", line 1342,... (1 Reply)
Discussion started by: programAngel
1 Replies
9. Shell Programming and Scripting
Hi Everyone,
we are running rsync with --backup mode, Are there any rsync options to remove backup folders on successful deployment?
Thanks in adv. (0 Replies)
Discussion started by: MVEERA
0 Replies
10. Ubuntu
the way that i use to backup my server is using the script below in ssh.
mysqldump --opt -Q -u username -p password > /var/www/squiro/sql/database.sql
but i want to set the server backup everyday at 1pm in same folder.
is that set it in crontab-e?
how to set it? (3 Replies)
Discussion started by: mampwamp
3 Replies
LEARN ABOUT DEBIAN
mojolicious::guides::codingguidelines
Mojolicious::Guides::CodingGuidelines(3pm) User Contributed Perl Documentation Mojolicious::Guides::CodingGuidelines(3pm)
NAME
Mojolicious::Guides::CodingGuidelines - Coding guidelines
OVERVIEW
This document describes the coding guidelines that are the foundations of Mojo and Mojolicious development.
Please do not send patches unless you agree with them.
MISSION STATEMENT
Mojo is a runtime environment for Perl real-time web frameworks. It provides all the basic tools and helpers needed to write simple web
applications and higher level web frameworks such as Mojolicious.
All components should be reusable in other projects and in a UNIXish way only loosely coupled.
Especially for people new to Perl it should be as easy as possible to install Mojolicious and get started. Writing web applications can be
one of the most fun ways to learn a language!
For developers of other web frameworks it should be possible to reuse all the infrastructure and just consider the higher levels of the
Mojolicious distribution an example application.
RULES
Web development should be easy and fun, this is what we optimize for.
The web is a moving target, to stay relevant we have to stay in motion too.
Keep it simple, no magic unless absolutely necessary.
The installation process should be as fast and painless as possible. (Less than a minute on most common hardware is a good rule of thumb)
The addition and modification of features is decided by majority vote or the pumpking.
Any core developer may nominate a new one, who must then be accepted by a 2/3 majority vote.
The pumpking has veto rights and may select his successor.
It's not a feature without a test and documentation.
A feature is only needed when the majority of the userbase benefits from it.
Features may only be changed in a major release or after being deprecated for at least 3 months.
Refactoring and deprecations should be avoided if no important feature depends on it.
New features can be marked as experimental to be excluded from deprecation policies.
A major release is signaled by a new major version number and a unique code name based on a unicode character.
Only add dependencies if absolutely necessary and make them optional if possible.
Domain specific languages should be avoided in favor of Perl-ish solutions.
No inline POD.
Documentation belongs to the guides, module POD is just an API reference.
The main focus of the included documentation should be on examples, no walls of text. (An example for every one or two sentences is a
good rule of thumb)
Everything should be ordered alphabetically if possible.
The master source code repository should always be kept in a stable state, use feature branches for actual development.
Code has to be run through Perl::Tidy with the included ".perltidyrc", and everything should look like it was written by a single person.
Code should be organized in blocks and those blocks should be commented.
No spaghetti code.
Comments should be correctly capitalized, and funny if possible, punctuation is optional if it doesn't increase readability.
Every file should contain at least one quote from "The Simpsons" or "Futurama".
No names outside of "Mojolicious.pm".
No Elitism.
Peace!
MORE
You can continue with Mojolicious::Guides now or take a look at the Mojolicious wiki <http://github.com/kraih/mojo/wiki>, which contains a
lot more documentation and examples by many different authors.
perl v5.14.2 2012-09-05 Mojolicious::Guides::CodingGuidelines(3pm)