Sponsored Content
Full Discussion: strange problem
Top Forums Shell Programming and Scripting strange problem Post 302552577 by frank_rizzo on Sunday 4th of September 2011 03:56:33 PM
Old 09-04-2011
the directory does not exist
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Strange problem.Please Help !

I¡¯m a network operator, mine is an IBM PC server 320, operating system SCO unix 3.2v4.2, triton 3.1 of Baan. Recently, my server went dead every a few hours, no sign & signal shows malfunction suddenly. It looks like a sudden power failure, but the indicator of main power supply is on. Normal... (1 Reply)
Discussion started by: lyhsm
1 Replies

2. UNIX for Dummies Questions & Answers

Strange Problem

I did an installation of Redhat 7.1 and it seem to install smoothly. I go and reboot and I get the following message: "INIT: Id "x" respawing too fast: disabled for 5 minutes" The screen flashes 4 times every 10 seconds or so. I can't seem to figure why this does this. It might be a simple... (2 Replies)
Discussion started by: forjohnny
2 Replies

3. UNIX for Dummies Questions & Answers

strange...problem

Hi.. Some of my application were not running properly due to lack of virtual memory.....so wht i did add one free harddisk as swap file system...and increased the swap memory.. But since than my root file system is showing 100% full thr is no space left...is thr any link between these two..... (1 Reply)
Discussion started by: Prafulla
1 Replies

4. Linux

very strange problem

I have installed Fedora Core on a Toshiba Satellite Pro4600 laptop recently I have experienced a rather mysterious problem if I touch anything specially the keyboard or mouse I see this stuff “67yujhnmyyy” straight away some time it won't stop for while like this... (5 Replies)
Discussion started by: kemobyte
5 Replies

5. Shell Programming and Scripting

Strange problem

I am using SunOS 5.9 and I don't know why all my commands are getting executed as if an extra 'enter' has been pressed. What could be the reason and how to correct it? Please help. Asty (2 Replies)
Discussion started by: Asty
2 Replies

6. Shell Programming and Scripting

Strange problem.

Well, my script started off to do what i wanted. Now, i think its not recognizing the pattern so its not moving anything. What i have to do is execute my script command for the move to take effect. So i did that and yayy it worked. Strange thing is that my DESTDIR was empty to begin with.... (2 Replies)
Discussion started by: oxoxo
2 Replies

7. UNIX for Dummies Questions & Answers

strange rlogin problem

Hi, in my environment we have several server with rlogin passwordless login enabled, now there is a problem to setup this with a hpux server. i have check the .rhosts file and kerberos key are all setup properly and permission is correct, even other user id on the server can login without... (3 Replies)
Discussion started by: robertngo
3 Replies

8. Shell Programming and Scripting

Strange Problem

Hi All, I am encountering an unexpected problem while running my process, using daemon placed in /etc/init.d/. I have a process that is opening shared library using dlopen. When I run my process on the command line, it is able to open the library. But when I used daemon to run my process, I... (0 Replies)
Discussion started by: qwerty-1
0 Replies

9. UNIX for Dummies Questions & Answers

strange problem with samba

windowsxp:192.168.0.11 fedora14:192.168.0.12, running smb server I have disabled selinux. user list of fedora14: jone (wihch is created when install fedora14, with password 'jone') jone2 (which is added by hand, with password 'jone2') I added jone and jone2 as samba users using 'smbpasswd... (1 Reply)
Discussion started by: vistastar
1 Replies
unlink(2)							System Calls Manual							 unlink(2)

NAME
unlink - remove directory entry; delete file SYNOPSIS
DESCRIPTION
The system call removes the directory entry named by the path name pointed to by path. When all links to a file have been removed and no process has the file open, the space occupied by the file is freed and the file ceases to exist. If one or more processes have the file open when the last link is removed, only the directory entry is removed immediately so that processes that do not already have the file open cannot access the file. After all processes close their references to the file, if there are no more links to the file, the space occupied by the file is then freed and the file ceases to exist. RETURN VALUE
returns the following values: Successful completion. Failure. is set to indicate the error. ERRORS
If fails, is set to one of the following values: Search permission is denied for a component of the path prefix. Write permission is denied on the directory containing the link to be removed. The process does not have read/write access permission to the parent directory. The entry to be unlinked is the mount point for a mounted file system. path points outside the process's allocated address space. The reliable detection of this error is implementation dependent. Too many symbolic links were encountered in translating the path name. The length of the specified path name exceeds bytes, or the length of a component of the path name exceeds bytes while is in effect. The named file does not exist (for example, path is null or a component of path does not exist). A component of the path prefix is not a directory. The directory containing the file to be removed has the sticky bit set and neither the containing directory nor the file to be removed are owned by the effective user ID. The named file is a directory and the effective user ID is not a user with appropriate privileges. Some file systems return this error whenever the named file is a directory, regardless of the user ID. The directory entry to be unlinked is part of a read-only file system. The entry to be unlinked is the last link to a pure procedure (shared text) file that is being executed. WARNINGS
If is used on a directory that is not empty (contains files other than and the directory is unlinked, the files become orphans, and the directory link count is left with an inaccurate value unless they are linked by some other directory. If is used on a directory that is empty (contains only the files and the directory is unlinked, but the parent directory's link count is left with an inaccurate value. In either of the above cases, the file system should be checked using (see fsck(1M)). To avoid these types of problems, use instead (see rmdir(2)). SEE ALSO
rm(1), close(2), link(2), open(2), rmdir(2), remove(3C), privileges(5). STANDARDS CONFORMANCE
unlink(2)
All times are GMT -4. The time now is 11:22 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy