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
Forums
Discussions
Discussions
Discussions
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
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
01-08-2006 07:54 PM
01-08-2006 07:54 PM
snd.*
Thanks for your help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-08-2006 08:05 PM
01-08-2006 08:05 PM
Re: snd.*
Where in the system did you find the files? (i.e. which directory?)
Use the "file" command to identify the type of the file. For example, enter "file snd.*". What does it say?
If it says just "data", the file is not of any known type and only the application that created it will know what's it for.
The style of the name suggests that it *might* be some kind of a temporary file. The 5-digit number *might* be a process ID number of the process that created the file. Have you had any application crash on you lately?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-08-2006 08:59 PM
01-08-2006 08:59 PM
Re: snd.*
The command file shows ascii.
It seems to be created by "ELM"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-08-2006 09:55 PM
01-08-2006 09:55 PM
Re: snd.*
You said it seems to be created by "ELM": if it's the same program I know, it's a character-based (= not graphic) email client program. If the elm program is still running, it may remove the files automatically when it exits.
If the program that created them is not running anymore, you can certainly remove the files. The command "fuser snd.*" will tell you if any program is currently accessing the files.
If you're unsure, you can check the contents of the files, for example by using the command "less snd.*". If the files are not owned by you, you'll have to use the root account to do that.
HOWEVER, since elm is an email program, the files very probably contain (parts of) email messages. Checking them out might be an illegal invasion of your user's privacy.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2006 12:54 AM
01-09-2006 12:54 AM
Re: snd.*
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2006 12:58 AM
01-09-2006 12:58 AM