I was trying to write proxy code but i here is a problem
typedef struct req_msg
{
char *host;//hostname
char *filename;//filename
char *modified;//date
char *data;
char *request;
}req_msg;
while(take_responce(req,request)!=0)
// take_responce gets responce from http server
//... (0 Replies)
Hi,
I am having sequence of process ids in one file.
My file contents is (Output of fuser someobject.so).
654 14583 17890 25902
This no. of processes may vary depends up on the object.
I want to check all the processes one by one. If i want to apply egrep, I need to... (3 Replies)
I have two files. One has:
ID# 0 a b c d e f g h i j k....................~2 milion columns
ID# 0 l m n o p q r s t u v....................~2 milion columns
.
.
.
~6000 lines
Other has:
ID# 1
or
ID# 2
.
.
~6000 lines (2 Replies)
Hi
Can anyone please help me in resolving my issue.
I have a file with entries like this
t9787ms 99970 22/08/2010 12:30 /www.google.com
t9788ms 99942 22/08/2010 12:40 /www.google.com
t4788ms 88942 22/08/2010 01:40 /www.google.com
there are around 5 lakh records of this type my requirement... (4 Replies)
Hello,
Could you please tell me if there are any books/tutorial on
gdbm programming with C for beginners.
So far, I've found few tutorials and one of those:
http://www.network-theory.co.uk/docs/gccintro/gccintro_22.html
is easy to understand but very short in treatment as it dealt with ... (6 Replies)
Hi
I have to replace a pattern found in the first uncommented line in a file. The challenge I'm facing is there are several such similar lines but I have to edit only the first uncommented line.
Eg:
#this is example
#/root/xyz:Old_Pattern
/root/xyz:Old_Pattern
/root/xyz:Old_Pattern
... (10 Replies)
Hello Unix Shell Script Experts,
I have a script that would mask the columns in .csv file or .txt file.
First the script will untar the .zip files from Archive folder and processes into work folder and finally pushes the masked .csv files into Feed folder.
Two parameters are passed
... (5 Replies)
Discussion started by: Mahesh G
5 Replies
LEARN ABOUT BSD
link
LINK(2) System Calls Manual LINK(2)NAME
link - make a hard link to a file
SYNOPSIS
link(name1, name2)
char *name1, *name2;
DESCRIPTION
A hard link to name1 is created; the link has the name name2. Name1 must exist.
With hard links, both name1 and name2 must be in the same file system. Unless the caller is the super-user, name1 must not be a directory.
Both the old and the new link share equal access and rights to the underlying object.
RETURN VALUE
Upon successful completion, a value of 0 is returned. Otherwise, a value of -1 is returned and errno is set to indicate the error.
ERRORS
Link will fail and no link will be created if one or more of the following are true:
[ENOTDIR] A component of either path prefix is not a directory.
[EINVAL] Either pathname contains a character with the high-order bit set.
[ENAMETOOLONG] A component of either pathname exceeded 255 characters, or entire length of either path name exceeded 1023 characters.
[ENOENT] A component of either path prefix does not exist.
[EACCES] A component of either path prefix denies search permission.
[EACCES] The requested link requires writing in a directory with a mode that denies write permission.
[ELOOP] Too many symbolic links were encountered in translating one of the pathnames.
[ENOENT] The file named by name1 does not exist.
[EEXIST] The link named by name2 does exist.
[EPERM] The file named by name1 is a directory and the effective user ID is not super-user.
[EXDEV] The link named by name2 and the file named by name1 are on different file systems.
[ENOSPC] The directory in which the entry for the new link is being placed cannot be extended because there is no space left on the
file system containing the directory.
[EDQUOT] The directory in which the entry for the new link is being placed cannot be extended because the user's quota of disk blocks
on the file system containing the directory has been exhausted.
[EIO] An I/O error occurred while reading from or writing to the file system to make the directory entry.
[EROFS] The requested link requires writing in a directory on a read-only file system.
[EFAULT] One of the pathnames specified is outside the process's allocated address space.
SEE ALSO symlink(2), unlink(2)4th Berkeley Distribution August 26, 1985 LINK(2)