Sponsored Content
Top Forums UNIX for Dummies Questions & Answers ulimit on sco release 3.2v5.0.4 Post 670 by Neo on Friday 22nd of December 2000 06:58:48 PM
Old 12-22-2000
Yes. Break the file up into smaller segments and read those segments.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

SCO UNIX System V/386, Release 3.2

I was just wondering if there is a way to recursive grep for something in this version of UNIX... so that I don't have to do it a directory at a time? (1 Reply)
Discussion started by: PBNOSGT
1 Replies

2. UNIX for Advanced & Expert Users

Sco Unix OpenServer Release 3.0

hi everybody I have got a set of sco unix open server release 3.0 flopyy disks series N1, N2, M1, P1...P43, Release notes.. ý did a fresh installation. but ý cant install ethernet card. when ý use netconfig-ad a chain -tcpip... there is a messge : the sco contain TCP/IP driver. and ý... (2 Replies)
Discussion started by: kaygusuz
2 Replies

3. UNIX for Dummies Questions & Answers

SCO 3.2v5.05Eb: ? on trimming strings

Greetings. If I have a file with the following format: joe__________blow 1313 mockingbird pl. Los Angeles________, CA. 90210 bill__________clinton 1234 doghouse New York__________, NY. 12345 (note: I underlined what are spaces in the list due to the fact the billboard spaces them... (4 Replies)
Discussion started by: gee-dub
4 Replies

4. UNIX for Dummies Questions & Answers

Installing SCO release supplement

I am a complete UNIX newbie (although trying desperately to learn) - I've tried to find the answer here and on the SCO support site but probably don't understand well enough to see that the answer is staring me in the face! So apologies if I am asking a question that has been asked a million times... (4 Replies)
Discussion started by: kath
4 Replies

5. UNIX for Dummies Questions & Answers

File size limit exceeded... SCO ulimit?

Hello - O/S is UnixWare 7.1.4 My prefered method of copying files between servers is 'rcp', which does not recognize symbolic links; therefore, files are duplicated many times over. To avoid this duplication, I would like to use 'tar' and/or 'cpio' and pipe them through 'rcp', but... (1 Reply)
Discussion started by: rm -r *
1 Replies

6. SCO

sco openserver release 5.0.5 installation problems on notebook

hello, i want to install release 5.0.5 on my notebook but the system hangs when extracing files from source media in fact after configuration all of setting please help me:confused: (1 Reply)
Discussion started by: hossein
1 Replies

7. SCO

Printing to Windows 7 using Samba 2.0.3 via VPN connection to SCO 3.2v5.0.6

I would like to know if anyone has a way to PRINT TO a printer attached to a Windows 7 PC, from SCO, while logged in via a VPN connection. I am able to attach to a Samba share on the SCO server for files while attached to the VPN, so I know my Samba is workling - but my print jobs return: ... (2 Replies)
Discussion started by: tbb999
2 Replies

8. SCO

UNIX SCO release 5.05 system does not boot

UNIX sco release 5.05 system does not boot: cannot open device hd(40)/boot stage 1 boot failure: error loading hd(40)/boot what to do? (1 Reply)
Discussion started by: Joaoalpande
1 Replies

9. UNIX for Advanced & Expert Users

UNIX SCO release 5.05 system does not boot

UNIX sco release 5.05 system does not boot: cannot open device hd(40)/boot stage 1 boot failure: error loading hd(40)/boot what to do? (5 Replies)
Discussion started by: Joaoalpande
5 Replies
plock(2)							System Calls Manual							  plock(2)

NAME
plock() - lock process, text, data, stack, or shared library in memory SYNOPSIS
DESCRIPTION
The system call allows the calling process to lock the text segment of the process (text lock), its data segment (data lock), or both its text and data segment (process lock) into memory. Stack segments are also locked when data segments are locked. Shared library text and shared library data segments (shlib lock) can also be locked. Locked segments are immune to all routine swapping. also allows these seg- ments to be unlocked. The effective user ID of the calling process must be a user with the privilege. op must be one of the following: Lock text and data segments into memory (process lock) Lock text segment into memory (text lock) Lock data segment into memory (data lock) Remove locks Lock shared library text and shared library data segments (shared library lock) Lock text, data and shared library text and shared library data segments into memory (process and shared library lock) Lock text, shared library text and shared library data segments into memory (text and shared library lock) Lock data, shared library text and shared library data segments into memory (data and shared library lock) Although and the family of functions may be used together in an application, each may affect the other in unexpected ways. This practice is not recommended. Security Restrictions Some or all of the actions associated with this system call require the privilege. Processes owned by the superuser have this privilege. Processes owned by other users may have this privilege, depending on system configuration. See privileges(5) for more information about privileged access on systems that support fine-grained privileges. RETURN VALUE
returns the following values: Successful completion. Failure. The requested operation is not performed. is set to indicate the error. ERRORS
If fails, is set to one of the following values. op is equal to and a process lock, a text lock, or a data lock already exists on the calling process. op is equal to and a text lock or process lock already exists on the calling process. op is equal to and a data lock, or process lock already exists on the calling process. op is equal to and no type of lock exists on the calling process. op is equal to and there are no unlocked shared library segments in the calling process. op is equal to and a process lock, a text lock, or a data lock already exists on the calling process. op is equal to and a text lock or process lock already exists on the calling process. op is equal to and a data lock, or process lock already exists on the calling process. op is not equal to one of the values specified in is not allowed in a window. See vfork(2). There is not enough lockable memory in the system to satisfy the locking request. The effective user ID of the calling process is not a user with the privilege. EXAMPLES
The following call to locks the calling process in memory: SEE ALSO
setprivgrp(1M), exec(2), exit(2), fork(2), getprivgrp(2), mlock(2), vfork(2), privileges(5). STANDARDS CONFORMANCE
plock(2)
All times are GMT -4. The time now is 03:55 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy