Sponsored Content
Top Forums UNIX for Dummies Questions & Answers how to share the unix file for other client 's access Post 302079501 by floopw on Tuesday 11th of July 2006 01:52:38 AM
Old 07-11-2006
thank you for your advice .
But could you give me more details for me to shorten the range . Smilie
 

9 More Discussions You Might Find Interesting

1. Linux

how i can share the file between unix or linux in windows ??

hello everybody i have one quetion :( about how i can share my file in windows to use it in linux explane i have to opreating system windows xp and linux fedore core and unix ( sun solaris 10 ) and i want to open me file that is storege in windows <<< want to open it in unix or... (4 Replies)
Discussion started by: msn22
4 Replies

2. AIX

Access windows share from AIX

How in AIX 5.1 can I access a windows shared drive without using NFS. I have looked into cifs but I can not seem to find the package that I need to install for AIX 5.1 if anyone can give me any further direction please let me know. (2 Replies)
Discussion started by: chefsride
2 Replies

3. AIX

AIX to access Windows share

Are there any special requirements/tools needed for a AIX server to see (copy data) a Windows share? Only need 1-way copy (Windows-to-AIX). (8 Replies)
Discussion started by: kirkb
8 Replies

4. Red Hat

Not able to mount NFS share on client side

When i tried to mount the nfs i see this error message mount -t nfs 192.168.20.194:/remote/proj1 /nfsmount mount: 192.168.20.194:/remote/proj1 failed, reason given by server: Permission denied and the /etc/exports file in the host side looks like this /remote/proj1 ... (12 Replies)
Discussion started by: srinathk
12 Replies

5. Windows & DOS: Issues & Discussions

Script that, if file exists in Samba share, moves file to Unix server

I'm looking to do pretty much what the title says. I want a script that runs, it can run on Unix or Windows, doesn't matter, and searches a Samba shares for a .txt file. If the file exists, the script will move (or possibly copy) the file from the Samba share into a directory on our Unix... (3 Replies)
Discussion started by: twcostello
3 Replies

6. Solaris

Can't access NFS Share on Solaris Server from a Linux Client

Hi, I am trying to access a NFS shared directory on Solaris 10 Server from a client which is RHEL 4 Server. On the NFS Server, in /etc/dfs/, I added following line to dfstab file. & then ran the following On the client machine, while running the mount command, I am... (0 Replies)
Discussion started by: SunilB2011
0 Replies

7. Red Hat

Unable to access NFS share on Solaris Server from Linux client

Hi, I am trying to access a NFS shared directory on Solaris 10 Server from a client which is RHEL 4 Server. On the NFS Server, in /etc/dfs/, I added following line to dfstab file. share -F nfs -o rw /var/share & then ran the following svcadm -v enable -r... (3 Replies)
Discussion started by: SunilB2011
3 Replies

8. UNIX for Advanced & Expert Users

How to get file from share drive when filename with spaces using samba client?

Hi Team, I am not able to get file name from shared drive when filename have spaces in it. following command i am using. filename="REP00105 - ABC XYZ (SCM)_ 1.TXT" /hfx/opt/samba220/bin/smbclient \\\\${nt_host}\\${nt_share} ${NT_PASSWORD} -U${NT_USERNAME} -c "cd ${nt_directory}; prompt;... (1 Reply)
Discussion started by: Makarand Dodmis
1 Replies

9. UNIX for Beginners Questions & Answers

Samba Share access from windows

Hello, I want to connect to two samba shares both on the same Linux box but each with a different username from a windows server 2008. I created 2 gpos to connect and I can connect to the shares individually via net use command, but once I entered credentials for one of the shares, it seems I... (1 Reply)
Discussion started by: zaineyma
1 Replies
MADVISE(2)						      BSD System Calls Manual							MADVISE(2)

NAME
madvise, posix_madvise -- give advice about use of memory SYNOPSIS
#include <sys/mman.h> int madvise(void *addr, size_t len, int advice); int posix_madvise(void *addr, size_t len, int advice); DESCRIPTION
The madvise() system call allows a process that has knowledge of its memory behavior to describe it to the system. The advice passed in may be used by the system to alter its virtual memory paging strategy. This advice may improve application and system performance. The behavior specified in advice can only be one of the following values: MADV_NORMAL Indicates that the application has no advice to give on its behavior in the specified address range. This is the system default behavior. This is used with madvise() system call. POSIX_MADV_NORMAL Same as MADV_NORMAL but used with posix_madvise() system call. MADV_SEQUENTIAL Indicates that the application expects to access this address range in a sequential manner. This is used with madvise() system call. POSIX_MADV_SEQUENTIAL Same as MADV_SEQUENTIAL but used with posix_madvise() system call. MADV_RANDOM Indicates that the application expects to access this address range in a random manner. This is used with madvise() system call. POSIX_MADV_RANDOM Same as MADV_RANDOM but used with posix_madvise() system call. MADV_WILLNEED Indicates that the application expects to access this address range soon. This is used with madvise() system call. POSIX_MADV_WILLNEED Same as MADV_WILLNEED but used with posix_madvise() system call. MADV_DONTNEED Indicates that the application is not expecting to access this address range soon. This is used with madvise() system call. POSIX_MADV_DONTNEED Same as MADV_DONTNEED but used with posix_madvise() system call. MADV_FREE Indicates that the application will not need the information contained in this address range, so the pages may be reused right away. The address range will remain valid. This is used with madvise() system call. MADV_ZERO_WIRED_PAGES Indicates that the application would like the wired pages in this address range to be zeroed out if the address range is deallocated without first unwiring the pages (i.e. a munmap(2) without a preceding munlock(2) or the application quits). This is used with madvise() system call. The posix_madvise() behaves same as madvise() except that it uses values with POSIX_ prefix for the advice system call argument. RETURN VALUES
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
madvise() fails if one or more of the following are true: [EINVAL] The value of advice is incorrect. [EINVAL] The address range includes unallocated regions. [ENOMEM] The virtual address range specified by the addr and len are outside the range allowed for the address space. LEGACY SYNOPSIS
#include <sys/types.h> #include <sys/mman.h> int madvise(caddr_t addr, size_t len, int advice); int posix_madvise(caddr_t addr, size_t len, int advice); The include file <sys/types.h> is necessary. The type of addr has changed. SEE ALSO
mincore(2), minherit(2), mprotect(2), msync(2), munmap(2), compat(5) HISTORY
The madvise function first appeared in 4.4BSD. The posix_madvise function is part of IEEE 1003.1-2001 and was first implemented in Mac OS X 10.2. BSD
June 9, 1993 BSD
All times are GMT -4. The time now is 03:25 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy