- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- HPE 9000 and HPE e3000 Servers
- >
- /dev/full
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-17-2005 02:06 PM
тАО08-17-2005 02:06 PM
which device does /dev/full connect to?
when the system will assign the /dev/full?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-18-2005 12:54 AM
тАО08-18-2005 12:54 AM
Re: /dev/full
I use /dev/null to zero out a log file that is in use. If a log file is too big, and needs to be reduced, you have to shut downthe application using it before reducing the size. /dev/null lets you get around that. It resets the file size to zero, and allows te logiing to continue. You do this via the following command
cat /dev/null > filename.log
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-18-2005 12:36 PM
тАО08-18-2005 12:36 PM
Re: /dev/full
crw-rw-rw- 1 bin sys 3 0x000003 Aug 17 12:37 full
#
it is true /dev/full
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-18-2005 01:38 PM
тАО08-18-2005 01:38 PM
Re: /dev/full
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-18-2005 01:42 PM
тАО08-18-2005 01:42 PM
Re: /dev/full
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-18-2005 06:53 PM
тАО08-18-2005 06:53 PM
SolutionCheck this page.
http://www.faqs.org/faqs/hp/hpux-faq/section-294.html
--
A device file with slightly similar behavior to /dev/zero can be created
on 10.x as follows:
# mknod /dev/full c 3 3
Reading from this device will always succeed and report that the
requested number of bytes were read. However, no data will actually be
copied to the read buffer.
--
Regards,
Robert-Jan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-19-2005 07:10 AM
тАО08-19-2005 07:10 AM
Re: /dev/full
# dd if=/dev/dsk/c2t2d0 of=/dev/null
it lights up the drive, without creating ginormous files.