Script execution is very slow when trying to find all files and their owners on HP-UX box
Hi,
I have a HP-UX server were I need to list all the files in the entire file system, their directory path, last modified date, owner and group. I do not need to search the file contents. I created the script given below and I am excluding directories and files of type tmp, temp and log. The issue I am facing is the script runs very fast for some minutes but slows down and adds only 1 or 2 records per second. Is that normal or can this be expedited by some script tweeking? My server is supposed to have more than 500000 files and with this speed, script execution is taking too much time. I believe since I am not searching the file contents and only fetching the file name and some of its attributes, it should be very fast.
I tried removing the print option but still the script execution is slow.
Last edited by Adyan Faruqi; 08-14-2015 at 04:51 PM..
Reason: spell check
Running open solaris on a e420 that I recently picked up. Having issues sshing to it from either of my Linux boxes as its very slow to login (from the solaris box to the linux box it connects just fine.
Here is the output of ssh -vvv. I have hightlighted where it seems the slowdown is. Does... (0 Replies)
i'm not much of an advanced unix programmer but I'm trying to write a script to access files on box1 after ssh from box 1 to box2. when ssh is invoked in the script i'm getting logged into box2 and losing complete touch with box1 which is normal i guess.
but my main aim with my script is when i... (3 Replies)
Hi !
Can somebody tell me why -or- when will a unix box will become slow in processing ....
where to go and chk the stats... for this ???
Pls help..
Thanks in advance... (2 Replies)
Dear World,
I just wrote a script, which puzzled me somewhat. The siginficant code was:
for file in `ls splits*`; # splits* came from a split command executed earlier
do
tail -$SomeNumber $file | cut -d" " -f6 > $file;
done;
The interesting thing is this: A few of the $files were... (2 Replies)
Basically my requirement is to know the total number of free anonymous ports.
anonymous port range is 32768- 65535.
i wrote a script for that
**********************************************
for i in {32768..65535}
do
netstat -an | grep $i > /dev/null
if
... (21 Replies)
My git post-update has the following lines in it to make sure the permissions are set right:
find /usr/local/apache/htdocs -type d -print0 | xargs -0 chmod 755
find /usr/local/apache/htdocs -type f -print0 | xargs -0 chmod 644
chown -R apache:apache /usr/local/apache/htdocsThe only problem is... (5 Replies)
I have to list the files in a directory and along with that, list the owner of each of those files. Can someone please help me with a way to get this info please?
Gayathri (2 Replies)
Gents,
Please can u help me to improve this script to be more faster, it works perfectly but for big files take a lot time to end the job..
I see the problem is in the step (while) and in this part the script takes a lot time..
Please if you can find a best way to do will be great.
... (13 Replies)
Discussion started by: jiam912
13 Replies
LEARN ABOUT ULTRIX
chmod
chmod(2) System Calls Manual chmod(2)Name
chmod, fchmod - change mode of file
Syntax
#include <sys/types.h>
#include <sys/stat.h>
chmod(path, mode)
char *path;
mode_t mode;
fchmod(fd, mode)
int fd;
mode_t mode;
Description
The file whose name is provided by path or referenced by the descriptor fd has its mode changed to mode. Modes are constructed by ORing
combinations of the following:
S_ISUID - 04000 set user ID on execution
S_ISGID - 02000 set group ID on execution
S_ISVTX - 01000 save text image after execution
S_IRUSR - 00400 read by owner
S_IWUSR - 00200 write by owner
S_IXUSR - 00100 execute (search on directory) by owner
S_IRWXG - 00070 read, write, execute (search) by group
S_IRWXO - 00007 read, write, execute (search) by others
If an executable file is set up for sharing (the default), the mode S_ISVTX prevents the system from abandoning the swap-space image of the
program-text portion of the file when its last user terminates. The ability to set this bit is restricted to the superuser.
If the mode S_ISVTX (sticky bit) is set on a directory, an unprivileged user cannot delete or the rename files of other users in that
directory. For more information on the sticky bit, see
Only the owner of a file or the superuser can change the mode.
Writing a file or changing the owner of a file clears the set-user-id and set-group-id bits of that file. Turning off these bits when a
file is written or its owner changed protects the file from remaining set-user-id or set-group-id after being modified. If a file, specifi-
cally a program, remained set-user-id or set-group-id after being modified, that file could allow unauthorized access to other files or
accounts.
Environment
System Five
ELOOP is a possible error condition.
Return Values
Upon successful completion, a value of 0 is returned. Otherwise, a value of -1 is returned, and is set to indicate the error.
Diagnostics
The system call fails and the file mode remains unchanged under the following conditions:
[EACCES] Search permission is denied on a component of the path prefix.
[EFAULT] The path argument points outside the process's allocated address space.
[EIO] An I/O error occurred while reading from or writing to the file system.
[ELOOP] Too many symbolic links were encountered in translating the pathname.
[ENAMETOOLONG] A pathname component exceeds 255 characters, or an entire pathname exceeds 1023 characters.
[ENOENT] The named file does not exist.
[ENOTDIR] A component of the path prefix is not a directory.
[EPERM] The effective user ID does not match the owner of the file and the effective user ID is not the superuser.
[EROFS] The named file resides on a read-only file system.
[ESTALE] The file handle given in the argument is invalid. Either the file referred to by that file handle no longer exists or it
has been revoked.
The system call fails under the following conditions:
[EBADF] The descriptor is not valid.
[EINVAL] The fd refers to a socket, not to a file.
[EIO] An I/O error occurred while reading from or writing to the file system.
[EROFS] The file resides on a read-only file system.
[ETIMEDOUT] A connect request or remote file operation failed because the connected party did not respond after a period of time deter-
mined by the communications protocol.
See Alsoopen(2), chown(2)chmod(2)