Sponsored Content
Top Forums Shell Programming and Scripting \n have to make a newline forever? Post 302394734 by maxlamax on Friday 12th of February 2010 10:44:12 AM
Old 02-12-2010
Thx all for the suggest...
I try right now...

P.S. Ugly but short and functional? What's the matter... Better than long and heavy... Ops! and beautiful obviously... Smilie
 

9 More Discussions You Might Find Interesting

1. AIX

AIX 4.3.3 takes forever to log in

Hi all, my RS/6k 7043 150 with aix 4.3.3 takes FOREVER to log in. When I power the machine on, the boot process procedes normally and I get 2 short beeps (which I don't recall hearing before) and then I get the login window. If I log in, as root, say, the machine goes to its usual blue screen... (3 Replies)
Discussion started by: Jwoollard
3 Replies

2. Programming

msgrcv pending forever !!!

When I am using msgrcv to get a message from a queue, in case of msgsnd some error, the msgrcv thread will waiting forever. Is there some way that I can specify a time out value for this queue ? just let msgrcv wait for some time, if no message comes during this time slot, msgrcv just return... (3 Replies)
Discussion started by: Yun Gang Chen
3 Replies

3. Solaris

user password forever

Hi I am very new for Solaris, I want to make some users' passwords never expired. My ssytem kernel is: 5.8 # uname -a SunOS sspfs_svr 5.8 Generic_117000-01 sun4u sparc SUNW,Netra-240 Could you make some advice? Thanks (5 Replies)
Discussion started by: xramm
5 Replies

4. UNIX for Dummies Questions & Answers

how can i make sar command run forever ?

Hello all i found out about the sar command but when looking in the man pages there is no way to make sar working for ever .. only with some kind of interval . like sar 2 30 . my question is can i just run sar for ever ? (5 Replies)
Discussion started by: umen
5 Replies

5. Linux

I want to mount my disk forever

Hi guys! I've just mounted my drive in fstab: /dev/sdb /myfolder ext3 defaults 0 0 and rebooted linux. I've got severel failers during booting process and also I can't login as root first time: login: root password:root incorrect login login:user password: user ... (1 Reply)
Discussion started by: Junior Admin
1 Replies

6. IP Networking

valid_lft forever preferred_lft forever <-- what does this mean?

Just looking at my ethernet interface.. I see this response... what does this mean...? ipconfig... lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft... (0 Replies)
Discussion started by: jimmyc
0 Replies

7. Programming

pthread_cond_timedwait relocks forever

looking in pthread's source code I can see that as an epilogue both pthread_cond_timedwait and pthread_cond_wait will try to relock the mutex by means of __pthread_mutex_cond_lock. Does this mean that any of them both could eventually block forever if the mutex is never again available after... (4 Replies)
Discussion started by: ramestica
4 Replies

8. Red Hat

Failed dependencies loop forever

Hello All, I was trying to install one rpm and it failed due to missing dependencies, when I try to look at the dependencies and try to install them it is asking for 100+ dependencies, did any one ever face this problem? how can we fix this? rpm -ivh /var/tmp/erlang-R15B-02.1.el6.x86_64.rpm... (0 Replies)
Discussion started by: lovesaikrishna
0 Replies

9. UNIX for Dummies Questions & Answers

Forever -w option

I am trying to use the forever command. I can get it to work if I do not use the w option to watch for changes and cause an automatic restart on a change to the contents of the directory being watched. I would really like to use the watch option. Is this option fully implemented? here is an... (4 Replies)
Discussion started by: barrygordon
4 Replies
creat64(2)							System Calls Manual							creat64(2)

NAME
creat64(), fstat64(), fstatvfs64(), getrlimit64(), lockf64(), lseek64(), lstat64(), mmap64(), open64(), pread64(), prealloc64(), pwrite64(), setrlimit64(), stat64(), statvfs64(), truncate64(), ftruncate64(), O_LARGEFILE - non-POSIX standard API interfaces to support large files SYNOPSIS
DESCRIPTION
New API's to support large files in 32-bit applications. These API interfaces are not a part of the POSIX standard and may be removed in the future. The function returns a file descriptor which can be used to grow the file past 2 GB if desired. All other functional behaviors, returns, and errors are identical to The function is identical to except that returns file status in a instead of a All other functional behaviors, returns, and errors are identical. The function is indentical to except that returns file status in a struct instead of a struct The function is identical to except that passes a as its second parameter instead of a All other functional behaviors, returns, and errors are identical. The function is identical to except that accepts an for the size parameter instead of All other functional behaviors, returns, and errors are identical. The function is identical to except that accepts an type as the desired offset and has a return value of All other functional behaviors, returns, and errors are identical. The function is identical to except that returns file status in a instead of All other functional behaviors, returns, and errors are identical. The function is identical to except that accepts the file offset as an The function opens files of any size. It returns a file descriptor which can be used to grow the file past 2 GB if desired. All other functional behaviors, returns, and errors are identical to The function is identical to except that accepts the file offset as an All other functional behaviors, returns, and errors are identical to The function is identical to except that accepts the file offset as an All other functional behaviors, returns, and errors are identical to The function is identical to except that accepts the file offset as an All other functional behaviors, returns, and errors are identical to The function is identical to except that passes a as its second parameter instead of a All other functional behaviors, returns, and errors are identical. The function is identical to except that returns file status in a instead of a Refer to The function is identical to except that accepts the length parameter as an instead of All other functional behaviors, returns, and errors are identical to The function is identical to except that accepts the length parameter as an instead of All other functional behaviors, returns, and errors are identical to Setting in a call to or is equivalent to calling or both of which set in the file status flags. This bit is automatically set by and if is set to 64. The bit may be queried by (or which can also turn the bit on or off if desired. APPLICATION USAGE
The standard POSIX interfaces may be used by 32-bit applications to create and access large files if compiled with set to 64. The interfaces described here are alternatives to the standard ones, and are enabled by defining For 64-bit applications, access to large files is automatic, as long as the underlying file system is enabled for large files. The inter- faces on this man page are available to 64-bit applications, for convenience in porting, but provide no additional capabilities. The exception is which is not visible to 64-bit applications. SEE ALSO
creat(2), thread_safety(5). creat64(2)
All times are GMT -4. The time now is 09:39 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy