File system full - what to look for : SUN

Generic info for SUN servers -
There are several reasons why a filesystem gets full. An important thing to consider is how you set up your filesystems during installation,;you need to take care how much space is used for each filesystem and think ahead.
With forward thinking it is less likely that your filesystems will get full, but will not prevent a filesystem getting full. This document will show the most common reasons why a filesystem may become full and how to handle them.Resolution Top
Below is written mainly to deal with the OS filesystems (such as root, var and usr), but it can be utilized to troubleshoot other filesystems. There are many ways of finding what's filling up a filesystem, which can sometimes be a difficult process. One problem is that a filesystem can be filled up by one or few very large files (which is generally easy to find) or by thousands of smaller files (which can be difficult to find and pinpoint the cause).
First you need to figure out which files are filling up your filesystem.

A very useful way to list the size of files in a filesystem is with the du command.
The following example lists files from largest to smallest on the root filesystem:
$ du -akd / sort -nr more
or
$ du -akd / sort -nr > /tmp/du.out

The latter will give you a file you can review at your convenience.
The -d option of the du command keeps du from crossing partition boundaries.
The “-a” option tells du to report file sizes (without this option du just reports the amount of space used in each directory. The “-k” option means that du will report in terms of kilobytes rather than 512-byte blocks. On Solaris 9 or later replace “k” with “h” if you prefer “human-readable” output, that is output in terms of kilobytes, megabytes or gigabytes depending on the number reported.
The -nr option of sort puts the files in reverse numerical order.
Of course, this can be used on filesystems other than root, just substitute the required path for “/” in the "du" command.

The command “du -skd /” summarizes the amount of kilobytes used for a filesystem, in the given case for the root filesystem. If this is different from what is reported by the df -k command, one may check the InfoDocs 4083 and 17720 for further explanation and troubleshooting tips.

One common problem with df showing more usage than du is existing data or files in directories that are used as mount points.
INFODOC 4083 covers this, but the basic solution is given again here for convenience.
Unmount any mounted filesystems and check the mount point directories for files. Remove the files, or move them if you think you need them, and mount the filesystems again.
For the /tmp filesystem, you will have to boot the system into single-user mode to access the /tmp directory without having swap mounted over it.
For /var and /usr, you will have to boot the system from cdrom, mount the root filesystem, and then check the /var and /usr directories under the mounted root filesystem. These should normally be empty when /var or /usr is not mounted.

Another good way to search for files is to use the command '/usr/bin/find'. There is a good document how to use the find command, see infodoc 13678
Standard filesystems to look at first will be:
Filesystem
Checks
/tmp
If /tmp is full or contains large files, a reboot will clean this directory. A default Solaris installation shares the diskspace for /tmp and swap as you can see in the output of the df command.
Note: /tmp is not cleaned at boot time if /tmp is configured as a separate filesystem.
/dev
Large files may appear here when trying to write to a device using the incorrect device name. For example /dev/rmt/o (letter 'o') instead of /dev/rmt/0 (digit 'zero' for a tape drive. This is a very common problem if the machine does not have a tape drive attached and someone uses a tape command like tar or ufsdump. That will just create a large file in /dev/rmt/. So be sure to check the /dev directory for actual links not files.
/
Look for core files. Check /.wastebasket and /lost+found directory for large files. Check for a .CPR file in root, this is put there by power suspend/resume software.
/var
Third party packages sometimes leave tar files in /var/sadm/pkg directory.
If /var is full (and is a separate filesystem) or /var directory is the one we determined is using up most space in root, check the following.
Clearing out (but NOT deleting; the files should be truncated to zero length) the following files might gain you some space. Use caution here because you will lose various log information. For example, the utmp[x] and wtmp[x] files contain user access and accounting information:
/var/cron/log
/var/spool/lp/logs
/var/adm/utmp
/var/adm/utmpx
/var/adm/wtmp
/var/adm/wtmpx
/var/log/syslog*
/var/adm/messages.*
NOTE: if you zero out the utmp, utmpx, wtmp or wtmpx files, you should reboot your machine.

To zero out a file:
# cat /dev/null > filename
NOTE: For Solaris[TM] 9 or greater, see logadm(1M) for a useful tool to manage log files.
Check /var/saf - check for _log and in tcp and zsmon directories. There will be _log files - you can zero them out with "cat /dev/null > filename". If your system is being used as a printer host, check /var/lp/logs for files, they can be removed if they have been printed or left over from system crashes or printer problems. Check /var/preserve. Check /var/spool/* directory. Subdirectories like "lp" or "mqueue" are used for spooling. Check /var/crash for any system cores. Also check /var/tmp for files not needed; /var/tmp is not cleaned up with a reboot.
A word of caution regarding the /var/sadm directory. This directory contains package and patch information and generally should not be touched.

Also it could be that you are running out of inodes and are getting the message “file system full”. In this case recreate a partition with more inodes. The basic steps are:

Remove unneeded files.*
Backup the partition.*
recreate using newfs -i nbpi /dev/ where nbpi is chosen smaller then the default for the disk size, and rfsname is the raw filesystem; e.g. /dev/rdsk/cNtNdNsN. See man newfs(1M) for more information.*

Restore information back to the partition.
In the course of normal system operation, the root and usr filesystems (or directories) are mostly static (do not grow over time). /var however, does grow over time (because it contains log files, package database, print and mail spoolers, etc.). The name “var” is in fact an abbreviation for “varying” or “variable” as the “/var” filesystem is intended for files which vary in size and content over time (see the filesystem(5) manual page for more details about this). It is good system administration practice to monitor log files to make sure they don't get too large.
If a filesystem suddenly fills up, that could have been caused by installing a new piece of software into a wrong directory.
Check any lost+found directory on any filesystem that is full.
Another approach would be to list files by their modification date (if the date of when the filesystem filled up is known).
# ls -lRt / more will list all the files and sort them by the modification dates.

It could also be that all of these action does not give the solution and the problem is actually that the filesystem is too small.

To check inode usage - df -F ufs -o iTo check how a filesystem was created - mkfs -m /dev/rdsk/cXtXdXsX

::ciao.

Michael Jackson : 1958 - 2009

Rest in peace and I hope that you are moonwalking wherever you are.
Thank you for the music.

Is a system in trusted mode? : hp-ux

How do you tell if a system is in trusted mode or not?

Try looking at these two:

#man iscomsec

#/usr/lbin/getprdef -r


:cheers!

Getting rid of stale nfs file handles : hp-ux

Run the command:

#fuser -uck /

:-)

Limiting the size of core dumps : hp-ux

To completely suppress core dumps:

Bourne-style shells: "ulimit -c 0"
C-style shells: "limit coredumpsize 0"

If you want to limit dumps to a specific size, specify a number instead of 0, in blocks for Bourne-style shells, or kilobytes for C-style shells.

:-)

Test ftp data transfer rate without actual transfererring

ftp targethost
username/passwd...
bin
hash
put "dd if=/dev/zero bs=32k count=1000" /dev/null

: ciao..

Employers still grapple over IT pay, skills

Despite recent changes in the global economy, the cost of hiring quality IT staff remains a challenge for employers, say human resource experts.

According to Sommer Owens, manager of IT contract division at Robert Walters Hong Kong, IT salaries in the Chinese territory have been holding steady, but some employees are prepared to lower their pay expectations.

"Candidates who have been caught up in corporate restructuring are willing to accept a lower salary than they were previously getting to stay competitive in...[the] market," Owens said in an e-mail interview.

However, E. Balaji, CEO of India-based recruitment agency Ma Foi Management Consultants, noted that while it is true the bargaining power has swung in favor of employers, the expanding workers pool and lowering salaries relate more to generic IT skills.

A year ago, Balaji explained in an e-mail, most prospective candidates had more than one job offer and candidates were aggressively negotiating salaries and benefits, thereby pushing up the cost of quality talent. "With the current slowdown, this has subsided," he said, adding that the economic downturn has provided cash-rich companies with the opportunity to recruit quality talent at optimal cost.

"[However], for specific levels of expertise and niche skills, potential candidates in a company are generally 'ring-fenced'. Hopes of attracting them at less attractive terms may not materialize," he noted.

Yeo Gek Cheng, director of IT and telecommunications at Hudson Singapore, said the perception that employers now have a wider pool of candidates from which to choose "cannot be further from the truth", particularly for mid- to senior hires who are strong in their field.

"Those who are gainfully employed are unwilling to move due to the perceived risk of changing jobs now," Yeo told ZDNet Asia in an e-mail, adding that employees' annual salary increments have also remained unchanged.

While businesses still face a challenge recruiting candidates, this is less of an issue now as there are fewer job offers available to IT professionals, she said. Yeo noted that the lack of candidates in Asia cannot be resolved simply by an economic downturn. "What is a tight labor pool remains tight," she added.

Agreeing, Owens said some IT skills are still in short supply.

by Sol E. Solomon, ZDNet Asia

read more -->http://www.zdnetasia.com/news/business/0,39044229,62054088,00.htm

Terminate a socket without terminating a process:HP-UX

PROBLEM

Terminate a socket without terminating a process

RESOLUTION

Refer to man page on ndd:

#man 1m ndd

ndd -h supported (will display supported ndd parameters)
ndd -h unsupported (will display unsupported ndd parameters)

Here is an example using the tcp_discon parameter:

#ndd -get /dev/tcp tcp_discon number

NOTE: This number is obtained by running the following command:

#ndd -get /dev/tcp tcp_status

The tcp_status will give you a long list of connected sockets. Find the one
that needs to be killed (use netstat -a (if you have the name of the
host, use the -n option if you have the IP of the host you are looking
for) and then compare to ouput of the -get command below to find the
hostname or the ip). Then use the number on the far left of the output
(LEADING ZEROS must be removed from the number) and prepend it with a 0x to
show its hex.

Example of commands:

* #ndd -get /dev/tcp tcp_status
* #ndd -set /dev/tcp tcp_discon 0x010203404

If using the tcp_discon_by_addr variable convert the ip address into the
hexadecimal representation.

#ndd -set /dev/tcp tcp_discon_by_addr [hex number]

Where '[hex number]' is the one that needs to be killed.

:ciao..

Crontab : HP-UX

Many times admins forget the field order of the crontab file
and alway reference the man pages over-and-over.

Make your life easy. Just put the field definitions in your crontab file
and comment (#) the lines out so the crontab file ignores it.

# minute (0-59),
# | hour (0-23),
# | | day of the month (1-31),
# | | | month of the year (1-12),
# | | | | day of the week (0-6 with 0=Sunday).
# | | | | | commands
3 2 * * 0,6 /some/command/to/run
3 2 * * 1-5 /another/command/to/run

export EDITOR=vi ;to specify a editor to open crontab file.

crontab -e Edit your crontab file, or create one if it doesn't already exist.
crontab -l Display your crontab file.
crontab -r Remove your crontab file.
crontab -v Display the last time you edited your crontab file. (This option is only available on a few systems.)


Here are some examples.

0 0 * * * -- midnight every day
0 0 * * 1-5 -- midnight every weekday
0 0 1,15 * * -- midnight on 1st and 15th of month
0 0 1 * 5 -- midnight on 1st of month and every Friday

Crontab example:

A line in crontab file like below removes the tmp files from /home/someuser/tmp each day at 6:30 PM.

30 18 * * * rm /home/someuser/tmp/*

Cheers !!!

Pacquiao Blows Out Hatton in Two

Sun, 03 May 2009...It was two rounds of brutal action and a two round blowout for Filipino sensation Manny “The Pacman” Pacquiao as he walked through, around, and all over Ricky “The Hitman” Hatton (45-2 with 32 KOs).

HP-UX How can I disable non-root logins?

Add the following to /etc/profile, then 'touch /etc/nologin'; this will disable all new logins, except by root:

uid=`id -u`
if [ -f /etc/nologin -a $uid -ne 0 ]; then
echo "Sorry, no logins allowed; try later!"
sleep 5
exit 0
fi

::gudluck!

Root Lost Password : HP-UX... ;)

... but... what if your system is trusted mode???
..you can use some steps of this procedure if you want re-stablish a password than can not be set by cyclic problems...

The steps to reactivate the root account:
1. Boot the system in to single user mode.
2. Mount /usr file systems.# mount /usr
Note: The file system might need file system check (fsck) before mounting.
3. Systems that are not using Trusted System security skip to step #4.For Trusted Systems (presence of a /tcb directory), follow these additionalsteps:
a) Use the following command to reactivate the 'root' account:# /usr/lbin/modprpw -k root
b) Use the 'modprpw' command to null the password, so that the passwd commanddoes not prompt for the old password.
10.x# /usr/lbin/modprpw -w "" root
11.x# /usr/sam/lbin/usermod.sam -F -p "" root
NOTE: To untrust the system, use: tsconvert -r
4. Change the root account password.# passwd root
5. Boot the system in to multi user mode.

fyi la....

HP-UX : Extract one file from a make_tape_Recovery

To check the contents of the recovery tape ( assuming the tar archive and 0m/n as device file )
# mt -f /dev/rmt/0mn rew
# mt -f /dev/rmt/0mn fsf 1
# tar tvf /dev/rmt/0m

To extract a file from the archive
# mt -f /dev/rmt/0mn rew
# mt -f /dev/rmt/0mn fsf 1
# tar xvf /dev/rmt/0m

:: Don't try this at work :-)

HP-UX File Processing

:: Viewing contents of a file

The cat (concatenate) command can be used to view the contents of a file.

% cat friends
Sally Johnson     123 Ellesmere Lane       Athens        GA  12876   (413)345-8976
Bob Beamon        913 Mockingbird Lane     Annapolis     MD  17701   (201)962-8765
Kim Smith         234 Working Street       Hollywood     CA  18765   (678)987-9876
%

You will find on large files that the output of cat will not fit on your screen. The output will scroll across the screen and you will not be able to view the information. The more command is used to display file information in screen sized chunks. If the file is more than one screen long the word -More- followed by the percentage of the file displayed is placed at the bottom of the screen. Press the SpaceBar to see the next screen of the file or press q or to quit. It is better to use more if your output is going directly to the screen and to use cat if your output is going to a file or pipe.

::Pattern Searching

The grep (global regular expression print) command is used to search for a particular word or phrase in a file. The format of the grep command is:

grep [options] string file(s)

Where string is the word, phrase or regular expression you want to find, and file is the file to be searched. Lets find all lines that contain the string Sally in our friends file.

% grep Sally friends
Sally Johnson     123 Ellesmere Lane       Athens        GA  12876   (413)345-8976
Sally Miller      510 Epping Way           Hobe Sound    FL  33455   (654)546-4526
%

To find a pattern that is more than one word long, enclose the string within single or double quotation marks.

% grep 'Sally Miller' friends
Sally Miller      510 Epping Way           Hobe Sound    FL  33455   (654)546-4526
%

So far we have seen how grep prints all lines which contain the given character string. The -v (invert) option instructs grep to print all lines except those which match the string. This is usefull when you want to remove lines from a file. Lets find all the lines in a file that do not contain the string Sally and place the output into the friends.new file.

% grep -v 'Sally' > friends.new
% more friends.new
Bob Beamon        913 Mockingbird Lane     Annapolis     MD  17701   (201)962-8765
Kim Smith         234 Working Street       Hollywood     CA  18765   (678)987-9876
Eddy Murphy       210 W. Hollywood         Los Angles    CA  90210   (876)238-9987
%

The grep command can be used with regular expressions to match a pattern.

% grep '26$' friends
Sally Miller      510 Epping Way           Hobe Sound    FL  33455   (654)546-4526
%

This will find all the lines that end in "26".

The grep command can search for a string in groups of files. When it finds a pattern that matches in more that one file, it prints the name of the file, followed by a colon before the line matching the pattern. The -i (ignore) option to grep will ignore the case.

% grep -i bob *
friends:Bob Beamon        913 Mockingbird Lane     Annapolis     MD  17701   (201)962-8765
friends.new:Bob Beamon        913 Mockingbird Lane     Annapolis     MD  17701   (201)962-8765
%

:: Comparisons between files

The cmp (compare) command is used to compare any two files, including executable files. The diff (differential file operator) command is used to display the differences between text files or directories. The order of the diff command is important. The format of the diff command is:

diff [options] old_file new_file diff [options] old_dir new_dir

The diff command will display a listing of the editing actions that need to be performed on the old file to change it into the new file. The three ways in which diff indicated changes to a file are a (lines are added), c (lines are changed) and d(lines are deleted). Lets find the difference between the friends and the friends.new files.

% diff friends friends.new
1d0
< Sally Johnson     123 Ellesmere Lane       Athens        GA  12876   (413)345-8976
4d2
< Sally Miller      510 Epping Way           Hobe Sound    FL  33455   (654)546-4526
%

This tells us that deletions need to be made to the friends file to get the friend.new file. The 1d0 tells us that line 1 of the friend file has to be deleted, and the 4d2 tells us that line 4 of the friend file has to be deleted.

The output of diff can be sent to the ed command to convert the first file into the second. In fact, the using diff with the -e option will produce output suitable for input to the ed command.

% diff -e friends friends.new > ed.script
% ( cat ed.script ; echo w ) | ed friends
415
249
% diff friends friends.new
%

If you eliminated the echo w command, ed would read the input from the cat ed.script, perform the operation and then exit. With the echo w command you are telling ed to write to the file friends. The semicolon between the cat ed.script and echo w tells the shell that these are separate commands.

:: Counting things in a file

The wc (word count) command counts the number of lines, words, and characters in a file. This is especially usefull for counting the number of lines of source code in a program orthe number of words in a document.

% wc friends
3 28 249 friends
%

The first number indicates the number of lines, followed by the number of words and the number of characters(including newlines).

:: Modifying character strings

The sed (stream editor) command reads lines, one by one, from an input file and applies a set of editing commands to the lines. The sed command is like grep except that it allows you to make changes to file. The format of the sed command is:

sed [options] action/string/newstring file(s)

% sed "s/(201)962-8765/(201)962-9999/" friends
Bob Beamon        913 Mockingbird Lane     Annapolis     MD  17701   (201)962-9999
Kim Smith         234 Working Street       Hollywood     CA  18765   (678)987-9876
Eddy Murphy       210 W. Hollywood         Los Angles    CA  90210   (876)238-9987
%

The s (substitute) option tells sed to substitute. We have changed the phone number. If we wanted to save these changes we would redirect the output to a file.

The sed command also accepts regular expressions.

% sed '/^$/d' hello.cc
#include 
main() {
cout << "Hello, cruel world! \n";
}
%

The d option is tells sed to delete. In this case we are using a regular expression to tell sed to remove all blank lines from our hello.cc file.

:: Sorting data in files

The sort command is used to sort the contents of a file into alphabetic or numerical order.

% sort +1 friends
Bob Beamon        913 Mockingbird Lane     Annapolis     MD  17701   (201)962-8765
Eddy Murphy       210 W. Hollywood         Los Angles    CA  90210   (876)238-9987
Kim Smith         234 Working Street       Hollywood     CA  18765   (678)987-9876
%

The +1 option tells sort to use the second field of the sort key rather than the beginning of the line. Fields are separated by whitespace, however you can use the -t option to separate by any character. The -n options tells sort to sort a numeric key, otherwise it will sort by the corresponding ASCii values.

Another command that is usefull when you are sorting is the uniq command. The uniq command will write only one instance of each line, whereas the sort will print every line. Usually the output of the sort command is piped to the uniq command.

---

::enjoy life...

Patch Cleanup HP-UX

There is a utility under /usr/sbin and it is called 'cleanup'. It provides the following functionality for 10.X patch management:

/usr/sbin/cleanup
Remove superseded patches from the system to reclaim space in /var.
Queries the user re trimming SD logfiles as well.

/usr/sbin/cleanup -F
Forces the removal of ALL Patch backups to reclaim space in /var (you cannot back out a patch out after this).

/usr/sbin/cleanup -t
Trim SD logfiles /var/adm/sw*.log to the most recent 5 entries.

/usr/sbin/cleanup -i
Remove overwritten patch entries from the SDUX IPD.

/usr/sbin/cleanup -d [absolute path to software depot]
Removes superseded patches from a software depot.

:: :-)

HP-UX:Dynamically Extend / and (or) /stand File Systems

Article on how to dynamically extend / and (or) /stand file systems :

http://www.symmetricwebsites.com/articles/HP-UX/hpuxDynamicallyExtendSlashAndOrStand.php

::enjoy

change IP's Addresses of cluster servers.

I followed these steps when I had change IP Address of my cluster servers.

Before you change the IP Address of your Server you must have all new ip's
when you want to go ahead.(of course..:-))
ex. Server ip and package ip.

Take backup of these directory and files

1./etc/cmcluster
2./etc/hosts
3./etc/rc.config.d/netconf

modify these files
1./etc/hosts # modify ipaddress
2./etc/rc.config.d/netconf # modify ipaddress and subnet
3./etc/cmcluster/cluster.conf # modify HEARTBEAT_IP

4./etc/cmcluster/packge/cipackage.conf # change SUBNET XX.XX.XX.XX
5./etc/cmcluster/packge/dbpackage.conf # change SUBNET XX.XX.XX.XX

6./etc/cmcluster/packge/cipackage.cntl # change IP[0]=XX.XX.XX.XX
change SUBNET[0]=XX.XX.XX.XX

7./etc/cmcluster/packge/cipackage.cntl # change IP[0]=XX.XX.XX.XX
change SUBNET[0]=XX.XX.XX.XX

8.rcp cluster.conf into /etc/cmcluster
rcp cluster.conf into other node same location

9.rcp these conf,cntl and config file into /etc/cmcluster/packge/
rcp ciVRP.conf,dbVRP.conf,ciVRP.cntl,dbVRP.cntl

10. restart the net for new ip
/sbin/init.d/net stop
/sbin/inti.d/net start

check all ipaddress which we have changed and check with linkloop also

11.cmcheckconf -v -C /etc/cmcluster/cluster.conf -P cipackage.conf -P dbpackage.conf
it should come with no error then go for the next step

12.cmapplyconf -v -C /etc/cmcluster/cluster.conf -P cipackage.conf -P dbpackage.conf

warning : ninenok is not liable if its not working for you!
pls. pray before doing this.

F.

Been busy the past months and now I'm back again..Thanks for visiting my blog, and rest assured I'll share whatever stuff I can dig with relation to unix, etc.

Treat your password like your toothbrush. Don't let anybody else use it, and get a new one every six months. ~Clifford Stoll

HP-UX: How Do I configure routing or add route?

You can use route command to configure routing. Syntax is as follows:
route add net {network-address} netmask {subnet} {router-address}

Let us assume your router address is 192.168.1.254 and network ID is 192.168.1.0/24, then you can type route command as follows:
# route add net 192.168.1.0 netmask 255.255.255.0 192.168.1.254

OR

To add a default route:
# route add default 192.168.1.254

Verify that (display) routing table is updated (display routing table):
# netstat -nr

Test it i.e. try to ping or send nslookup request:
# ping mycorp.com

To flush all routing entries use command:
# route -f

However if I reboot HPUX box then above routing entries gets removed. To pick up your setting upon each reboot your need to configure Routes in HPUX networking configuration file - /etc/rc.config.d/netconf. To add default router/gateway 192.168.1.254:
# vi /etc/rc.config.d/netconf

Add or modify following entries

ROUTE_DESTINATION[0]="default"
ROUTE_MASK[0]=""
ROUTE_GATEWAY[0]="192.168.1.254"
ROUTE_COUNT[0]="1"
ROUTE_ARGS[0]=""

Reboot HP-UX system/server to take effect
# shutdown -ry 0

Finding file and directories : HP-UX

The find command recursively descends a directory locating all the files that meet the criteria given on the command line. Without any options the find command will take no action on the files it finds, so the -print option is used to write the found files to standard output. The format of the find command is:

find path_name_list [options]

Where path_name_list is one or more directories.

% find . -name Makefile -print
/home/huron2/admin/scot/tutorial/Makefile
%

The . is a directory abbreviation for the current directory. The -name option specifies that only files with the given name should be found. The name option can include wildcard character:

% find . -name "core*" -size +3 -mtime +7 -exec rm -i {} \; -print
/home/huron2/admin/scot/core: ? (y/n) y
/home/huron2/admin/scot/core
%

==>Some Options to Find
--------------------------------------------------------------------
-name file Find files named file

-size n         Find files that contain size...
                n  exactly n blocks (1 block = 512 bytes)
           +n  more than n blocks
           -n  less than n blocks

-mtime n        Find files that were modified
                n  exactly n days ago
           +n  more than n days ago
           -n  less than n days ago

-exec cmd Execute command cmd on each file

-type type   Find files that match the type
     f  ordinary file
     d  directory
     b  block device
     c  character device
     p  named pipe
--------------------------------------------------------------------

Actions can be taken when files are found by using the -exec option. The -exec option uses the {} (left curly-brace right curly-brace) syntax to specify the current file that find has found. The exec command ends with the \; syntax. If we did not have the print option at the end we would not get a confirmation the file had been removed.

...ciao...