VOP_IOCTL(9) BSD Kernel Developer's Manual VOP_IOCTL(9)NAME
VOP_IOCTL -- device specific control
SYNOPSIS
#include <sys/param.h>
#include <sys/vnode.h>
int
VOP_IOCTL(struct vnode *vp, u_long command, caddr_t data, int fflag, struct ucred *cred, struct thread *td);
DESCRIPTION
Manipulate a file in device dependent ways.
Its arguments are:
vp The vnode of the file (normally representing a device).
command The device specific operation to perform.
data Extra data for the specified operation.
fflag Some flags ???
cred The caller's credentials.
td The calling thread.
Most file systems do not implement this entry point.
LOCKS
The file should not be locked on entry.
RETURN VALUES
If successful, zero is returned, otherwise an appropriate error code.
If the ioctl is not recognized or not handled, ENOTTY should be returned.
SEE ALSO vnode(9)AUTHORS
This manual page was written by Doug Rabson.
BSD July 24, 1996 BSD
Check Out this Related Man Page
VOP_ACCESS(9) BSD Kernel Developer's Manual VOP_ACCESS(9)NAME
VOP_ACCESS, VOP_ACCESSX -- check access permissions of a file or Unix domain socket
SYNOPSIS
#include <sys/param.h>
#include <sys/vnode.h>
int
VOP_ACCESS(struct vnode *vp, accmode_t accmode, struct ucred *cred, struct thread *td);
int
VOP_ACCESSX(struct vnode *vp, accmode_t accmode, struct ucred *cred, struct thread *td);
DESCRIPTION
This entry point checks the access permissions of the file against the given credentials.
Its arguments are:
vp The vnode of the file to check.
accmode The type of access required.
cred The user credentials to check.
td The thread which is checking.
The accmode is a mask which can contain flags described in <sys/vnode.h>, e.g. VREAD, VWRITE or VEXEC. For VOP_ACCESS(), the only flags
that may be set in accmode are VEXEC, VWRITE, VREAD, VADMIN and VAPPEND. To check for other flags, one has to use VOP_ACCESSX() instead.
LOCKS
The vnode will be locked on entry and should remain locked on return.
RETURN VALUES
If the file is accessible in the specified way, then zero is returned, otherwise an appropriate error code is returned.
ERRORS
[EPERM] An attempt was made to change an immutable file.
[EACCES] The permission bits the file mode or the ACL do not permit the requested access.
SEE ALSO vaccess(9), vaccess_acl_nfs4(9), vaccess_acl_posix1e(9), vnode(9)AUTHORS
This manual page was written by Doug Rabson.
BSD September 18, 2009 BSD
The UNIX and Linux Forums have a number of active members that have published books or papers related to shell programming and scripting. You can check out their publications here:
Link Removed
Please note, as you can imagine, our forum experts can be quite busy! You will get a response... (0 Replies)
Emergency UNIX and Linux Support !! Help Me! Forum (Request Urgent Help)
README FIRST: How to Request Emergency or Urgent Help:
You may post emergency work-related questions in the emergency forum. To post in this forum you will need to use your Bits. All questions answered on a "best... (0 Replies)
Homework Help:
On Posting Questions:
Any and all high school and undergraduate homework assignments or textbook style exercises for which you are seeking assistance are to be posted only in our Homework & Coursework Questions area--not in blogs, visitor messages, PMs, or the main technical... (0 Replies)
Dear Forum Members,
The UNIX and Linux Forums are working directly with the Red Cross to provide ad banners on our site to support Earthquake and Tsunami Relief in Japan. Registered users do not see these banners. However, if you wish to contribute directly on behalf of yourself and the... (8 Replies)
How to Use Code Tags in The UNIX and Linux Forums
Developer: This video tutorial was created by scott for forum users. Everyone should use code tags when posting code and command line logic in the forums.
cPF45jjWe7Q
A full list of BB codes is available here. (8 Replies)
RULES OF THE UNIX AND LINUX FORUMS
For the latest version of the community rules (the official community rules page), please visit here.
No flames, shouting (all caps), sarcasm, bullying, profanity or arrogant posts.
No negative comments about others or impolite remarks. Be patient. No... (1 Reply)
I see lot of ad-hoc shell scripts in our servers which don't have a shebang at the beginning .
Does this mean that it will run on any shell ?
Is it a good practice to create scripts (even ad-hoc ones) without shebang ? (16 Replies)
Having spent a lot of time over the past year taking a legacy vBulletin site (this forum) and making the site responsive on mobile; I've happy with the results; but it will soon be time to move on.
Basically, at our core, we are a LAMP (Linux, Apache2, MySQL and PHP) site, and vBulletin was... (6 Replies)
Here are some answers to some of the recent questions I have received about UNIX.COM. So, I thought I would take time to answer them here in this post:
Is it expected that the original poster "thank" everyone who responds to his / her discussion thread?
It is always a good practice in all... (7 Replies)
By special request, and long overdue, I have updated our "code tags" video and so now we have:
How to Use Code Tags and Format Posts @UNIX.com in 4K
https://youtu.be/4BuPvWJV__k (3 Replies)
Here is a quick EOY report for 2019.
2019 has been a year of "downward trend reversal" for UNIX.com. In fact, if we compare total Google search impressions from the peak days in December 2019 to the peak days in mid December 2018, traffic is up 43% percent. That is a very respectable growth... (0 Replies)