07-29-2008
got it fixed. Systems were using automount.
Jim
10 More Discussions You Might Find Interesting
1. Solaris
hi all,
in my server there are some specific application files which are spread through out the server... these are spread in folders..sub-folders..chid folders...
please help me, how can i find the total size of these specific files in the server... (3 Replies)
Discussion started by: abhinov
3 Replies
2. Shell Programming and Scripting
Hi All...
is the below command be modified in sucha way that i can get the file size along with the name and path of the file
the below command only gives me the file location which are more than 100000k...but I want the exact size of the file also..
find / -name "*.*" -size +100000k
... (3 Replies)
Discussion started by: rpraharaj84
3 Replies
3. Solaris
Hi,
We currently have an Oracle database running and it is creating lots of processes in the /proc directory that are 1000M in size. The size of the /proc directory is now reading 26T. How can this be if the root file system is only 13GB?
I have seen this before we an Oracle temp file... (6 Replies)
Discussion started by: sparcman
6 Replies
4. Shell Programming and Scripting
#!/bin/sh
##########################################################################################################
#This script is being used for AOK application for cleaning up the .out files and zip it under logs directory.
# IBM
# Created
#For pdocap201/pdoca202 .out files for AOK
#1.... (0 Replies)
Discussion started by: mridul10_crj
0 Replies
5. Shell Programming and Scripting
Hi Experts,
I have a script like
$ORACLE_HOME/bin/sqlplus username/password # << ENDSQL
set pagesize 0 trim on feedback off verify off echo off newp none timing off
set serveroutput on
set heading off
spool Schemaerrtmp.txt
select ' TIMESTAMP COMPUTER NAME ... (5 Replies)
Discussion started by: welldone
5 Replies
6. Programming
Hi,
Can I find size of the file from size of the buffer written?
nbECRITS = fwrite(strstr(data->buffer, ";") + 1, sizeof(char), (data->buffsize) - LEN_NOM_FIC, fic_sortie);
Thank You :) (1 Reply)
Discussion started by: ezee
1 Replies
7. UNIX for Advanced & Expert Users
Hello,
in one default UFS filesystem we have 8K block size (bsize) and 1K fragmentsize (fsize). At this scenary I thought all "FileSytem IO" will be 8K (or greater) but never smaller than the fragment size (1K). If a UFS fragment/blocksize is allwasy several ADJACENTS sectors on disk (in a ... (4 Replies)
Discussion started by: rarino2
4 Replies
8. Solaris
Hi,
the /tmp size is less whereas the size allocated to swap is quite big. how to increase the size of /tmp -
#: swap -l
swapfile dev swaplo blocks free
/dev/md/dsk/d20 85,20 8 273096 273096
#: swap -s
total: 46875128k bytes allocated + 2347188k reserved =... (2 Replies)
Discussion started by: psb74
2 Replies
9. UNIX for Dummies Questions & Answers
I have been searching both on Unix.com and Google and have not been able to find the answer to my question. I think it is partly because I can't come up with the right search terms.
Recently, my virtual server switched storage devices and I think the problem may be related to that change.... (2 Replies)
Discussion started by: jmgibby
2 Replies
10. HP-UX
Accordingly a lot of manuals - if you have block size 8KB and trying to write a 1KB file to the block, as result you waste 7KB of the block space. But recently I noticed about Fragments of File Block. In same case if you have File Block 8KB and Fragment size 1KB - you can save your block space,... (6 Replies)
Discussion started by: jess_t03
6 Replies
LEARN ABOUT OPENSOLARIS
systemd.automount
SYSTEMD.AUTOMOUNT(5) systemd.automount SYSTEMD.AUTOMOUNT(5)
NAME
systemd.automount - Automount unit configuration
SYNOPSIS
automount.automount
DESCRIPTION
A unit configuration file whose name ends in ".automount" encodes information about a file system automount point controlled and supervised
by systemd.
This man page lists the configuration options specific to this unit type. See systemd.unit(5) for the common options of all unit
configuration files. The common configuration items are configured in the generic [Unit] and [Install] sections. The automount specific
configuration options are configured in the [Automount] section.
Automount units must be named after the automount directories they control. Example: the automount point /home/lennart must be configured
in a unit file home-lennart.automount. For details about the escaping logic used to convert a file system path to a unit name see
systemd.unit(5). Note that automount units cannot be templated, nor is it possible to add multiple names to an automount unit by creating
additional symlinks to its unit file.
For each automount unit file a matching mount unit file (see systemd.mount(5) for details) must exist which is activated when the automount
path is accessed. Example: if an automount unit home-lennart.automount is active and the user accesses /home/lennart the mount unit
home-lennart.mount will be activated.
Automount units may be used to implement on-demand mounting as well as parallelized mounting of file systems.
IMPLICIT DEPENDENCIES
The following dependencies are implicitly added:
o If an automount unit is beneath another mount unit in the file system hierarchy, both a requirement and an ordering dependency between
both units are created automatically.
o An implicit Before= dependency is created between an automount unit and the mount unit it activates.
DEFAULT DEPENDENCIES
The following dependencies are added unless DefaultDependencies=no is set:
o Automount units acquire automatic Before= and Conflicts= on umount.target in order to be stopped during shutdown.
FSTAB
Automount units may either be configured via unit files, or via /etc/fstab (see fstab(5) for details).
For details how systemd parses /etc/fstab see systemd.mount(5).
If an automount point is configured in both /etc/fstab and a unit file, the configuration in the latter takes precedence.
OPTIONS
Automount files must include an [Automount] section, which carries information about the file system automount points it supervises. The
options specific to the [Automount] section of automount units are the following:
Where=
Takes an absolute path of a directory of the automount point. If the automount point does not exist at time that the automount point is
installed, it is created. This string must be reflected in the unit filename. (See above.) This option is mandatory.
DirectoryMode=
Directories of automount points (and any parent directories) are automatically created if needed. This option specifies the file system
access mode used when creating these directories. Takes an access mode in octal notation. Defaults to 0755.
TimeoutIdleSec=
Configures an idle timeout. Once the mount has been idle for the specified time, systemd will attempt to unmount. Takes a unit-less
value in seconds, or a time span value such as "5min 20s". Pass 0 to disable the timeout logic. The timeout is disabled by default.
SEE ALSO
systemd(1), systemctl(1), systemd.unit(5), systemd.mount(5), mount(8), automount(8), systemd.directives(7)
systemd 237 SYSTEMD.AUTOMOUNT(5)