directory file number

[augusto cossa]

Hi

1ST:
I would like to know if it's possible to know the number of files that each directory can support. e.g. /home how many files support? the nfile tells me the max. number of open files in the system but not in the specific directory.

2ND:
I'm trying to perform backup by using SAM to a remote server but does not work. The message is displayed:

br_backup: Invoking fbackup. See /var/sam/log/br_log for details.
fbackup(1421): no history is available for graph file /etc/sam/br/graphFBAa21662 (below level 0)
fbackup(1004): session begins on Tue Oct 31 11:16:34 2000
fbackup(3301): could not open output file mem01:/dev/rmt/0mb
fbackup(3019): would you like to enter a new output file?

3RD:
Is there anywhere where we can found the explanation of error cods? I meaning if you issue a command ls -latr and the output is (cannot make a pipe error 23322) where to found the explanation of the cod error displayed?

Help on please.

Augusto

[Andreas Voss]

Hi,

to your 1st question please look at this thread:
http://forums.itrc.hp.com/cm/QuestionAnswer/1,1150,0x16e1f841489fd4118fef0090279cd0f9,00.html

Regards

[Mark Duffy]

2nd questtion:

Make sure that the remote server has an entry in .rhosts to allow connection from the server running the fbackup

[Mark Duffy]

2nd question:

Make sure that the remote server has an entry in .rhosts to allow connection from the server running the fbackup

[Mark Duffy]

2nd:

Make sure the server with the remote tape drive has an entry in .rhosts to allow the fbackup server to connect to it.

[Andreas Voss]

?

[federico_3]

about the second question:

some error codes can be found in :

/usr/include/sys/errno.h

federico

[federico_3]

....sorry the third question i wanted to tell.......


federico

[James R. Ferguson]

Augusto:

As regards your third question:

Non-normal exit codes often turn out to
be "errno" values, found in /usr/include/sys/errno.h.

This file has a mapping of number vs. name. For a brief, geneneral explanation of the error number, see man (2) errno. For specific information you must see the man page for the actual command that returns the error.

...JRF...

[James R. Ferguson]

Augusto:

As regards your third question:

Non-normal exit codes often turn out to
be "errno" values, found in /usr/include/sys/errno.h.

This file has a mapping of number vs. name. For a brief, geneneral explanation of the error number, see man (2) errno. For specific information you must see the man page for the actual command that returns the error.

...JRF...

[James R. Ferguson]

Augusto:

As regards your third question:

Non-normal exit codes often turn out to
be "errno" values, found in /usr/include/sys/errno.h.

This file has a mapping of number vs. name. For a brief, geneneral explanation of the error number, see man (2) errno. For specific information you must see the man page for the actual command that returns the error.

...JRF...

[James R. Ferguson]

Augusto:

As regards your third question:

Non-normal exit codes often turn out to
be "errno" values, found in /usr/include/sys/errno.h.

This file has a mapping of number vs. name. For a brief, geneneral explanation of the error number, see man (2) errno. For specific information you must see the man page for the actual command that returns the error.

...JRF...