Hi all,
I have to test some user priviliges. The goal is to be sure that an unauthorized user can't restart some modules (ssh, mysql etc...).
I'm trying to automate it with a shell script but in same cases I got the syslog broadcast message.
Is there any way to simply get a return code... (3 Replies)
Hello all,
If anyone has time, I have a few questions:
How do I do the following in Linux. We are using Red Hat and Oracle Enterprise Linux, which is based on Red Hat too.
1. How to lock the account after a few (like 3) invalid password attempts?
2. How do you lock a screen after 30... (1 Reply)
I have two laptops on which I've installed Ubuntu Studio 9.04. The first laptop (Acer) has a Centrino 32-bit Intel CPU in it and the second (HP) has a 64-bit dual core Intel CPU. I'm running the 32-bit version of Ubuntu Studio on the Acer and the 64-bit version on the HP. While testing the... (5 Replies)
Hi All,
I am trying to install the IBM data set generator. I have to use the Solaris to use this tool. The following link is supposed to tell the steps on how to use the IBM tool on the Solaris server.
IBM Quest Market-Basket Synthetic Data Generator
Unfortunately, I don't understand what is... (2 Replies)
how can I lock my keyboard while I'm away from the computer without using lock command. What other commands gives me the option to lock keyboard device?
thanks (7 Replies)
plock(2) System Calls Manual plock(2)Name
plock - lock or unlock process, text, or data in memory
Syntax
#include <sys/lock.h>
int plock (op)
int op;
Description
The call allows the calling process to lock its text segment (text lock), its data segment (data lock), or both its text and data segments
(process lock) into memory. Locked segments are immune to page outs, and the process is immune to swap outs. The call also unlocks these
segments.
The op argument specifies the following:
PROCLOCK Lock text and data segments into memory (process lock)
TXTLOCK Lock text segment into memory (text lock)
DATLOCK Lock data segment into memory (data lock)
UNLOCK Remove locks
Return Values
Upon successful completion, a value of 0 is returned to the calling process. Otherwise, a value of -1 is returned, and errno is set to
indicate the error.
Diagnostics
The call fails under the following conditions:
[EPERM] The effective user ID of the calling process is not superuser.
[EINVAL] The op argument is equal to PROCLOCK, and a process lock, a text lock, or a data lock already exists on the calling process.
[EINVAL] The op argument is equal to TXTLOCK, and a text lock or a process lock already exists on the calling process.
[EINVAL] The op argument is equal to DATLOCK, and a data lock or a process lock already exists on the calling process.
[EINVAL] The op argument is equal to UNLOCK, and no type of lock exists on the calling process.
Restrictions
The effective user ID of the calling process must be superuser to use this call.
Both PROCLOCK and TXTLOCK lock the text segment of a process, and a locked text segment is locked for all sharing processes.
Because the effective user ID of the calling process is superuser, take care not to lock more virtual pages than can be contained in physi-
cal memory. A deadlock can result.
See Alsoexecve(2), exit(2), fork(2), shmctl(2)plock(2)