Sponsored Content
Full Discussion: silent telnet
Top Forums UNIX for Dummies Questions & Answers silent telnet Post 6849 by cgardiner on Thursday 13th of September 2001 02:33:26 PM
Old 09-13-2001
Data silent telnet

I have been using the following code for sending out an email from a AIX UNIX platform.

cat filename | telnet mailhost 25 >/dev/null

Time to time I get a message

loopback: A specified file does not support the ioctl system call.

Can anyone tell me what this means? I need this function to be silent or it will be a problem since it is a cron task.

Is mpack an answer?.. this file is not an attachment. The file is in HTML format with MIME headers.
 

10 More Discussions You Might Find Interesting

1. HP-UX

SFTP silent login

Hi, I am connecting via SFTP to a remote Server. My problem is on trying to LOGin, I am asked for a password. I need to make this process automatic such that I can login without being prompted for a password. I can achieve this if the remote server has a simple FTP server and not SFTP. How... (6 Replies)
Discussion started by: sgaucho
6 Replies

2. Shell Programming and Scripting

[Perl] Silent Input

I would like to use the WWW::Mechanize module to access a webpage that is password-protected. I was wondering if there was a way to make the input silent when asked from the script. For example: What is your password: <password> Where <password> is where you put your password, but is silent... (2 Replies)
Discussion started by: eightysix
2 Replies

3. Linux

Wine in silent mode

I want to run through wine the utorrent and I don't want the messages that are usually displayed in the console, so I use the following command wine utorrent.exe > /dev/null & but it doesn't seem to work. Especially the redirection of the messages to the /dev/null doesn't work at all. Do... (1 Reply)
Discussion started by: myle
1 Replies

4. Linux

How to do a silent installation on linux

Hi, I am trying to do a silent installation of a JDk on a linux machine. Can anyone give me a command that would do it for me. Thanx Sundeep (2 Replies)
Discussion started by: eamani_sun
2 Replies

5. Shell Programming and Scripting

Silent Background Process

I run a background process using '&'. (see example below) How can I suppress the '&' messages that are written to my console?? (lines 2 and 5) Current Output... 1 > ak@LATU ~> ls & 2 > 4000 3 > ak@LATU ~> 4 > apps/ dl/ gems/ todo/ tst/ util/ 5 > + Done ... (1 Reply)
Discussion started by: andy210
1 Replies

6. UNIX for Advanced & Expert Users

FreeBSD silent port upgrade

I am using either portupgrade (/usr/ports/ports-mgmt/portupgrade) or portmaster (/usr/ports/ports-mgmt/portmaster) to upgrade the ports on the FreeBSD machines. However, this upgrade is not silent. Can anyone tell me how to make the upgrade silent? (0 Replies)
Discussion started by: figaro
0 Replies

7. Shell Programming and Scripting

Run a script in silent mode

Hi All, I have a script which calls some other scripts.. When i run the parent script all the status messages are displaying on terminal. I want to know how to suppress dem... or run a script in silent mode Thanks, Firestar (4 Replies)
Discussion started by: firestar
4 Replies

8. Shell Programming and Scripting

silent telnet and ssh using perl

Hi Experts, I use perl telnet and ssh for normal tasks and health checks. everything works fine but i would like to run scripts silently and print only data as i wish to. by silent i mean.no banners /no prompts/ nothing. I will format data before i print it on screen. just formatted... (3 Replies)
Discussion started by: mtomar
3 Replies

9. Shell Programming and Scripting

silent Input in PERL

Hello Experts, I am learning perl. I know ksh/bash/csh... In ksh I use to do this way... to read user input in silent mode so that nothing returns on the screen. stty -echo read -r pswd stty echo Please let me know the way in perl how to do it. Here are my OS and Perl Details... ... (3 Replies)
Discussion started by: explorer007
3 Replies

10. Shell Programming and Scripting

OSX read silent with prompt

A minor nitpick, but I cannot get a statement like: read -s -n 1 -p "Say Y or N here" -e ANS to actually hush the response. If I don't use the -p option, the response is silent. With it, I always see the response, and I've tried putting the -s in different spots. Is this a known issue, or... (2 Replies)
Discussion started by: jnojr
2 Replies
UUENVIEW(1)						      General Commands Manual						       UUENVIEW(1)

NAME
uuenview - a powerful encoder for binary files SYNOPSIS
uuenview [options] file(s) DESCRIPTION
uuenview encodes a binary file into ASCII text for sending over non-8-bit electronic data channels, such as electronic mail or the usenet. uuenview is a superset of and fully backwards compatible with the standard uuencode(1) command, featuring more comfort and more flexibil- ity. Files encoded with uuenview are compatible with virtually all decoders, as long as the encoding method (see below) is supported by the remote side. If the remote side uses uudeview(1), there shouldn't be any problems at all. If properly configured, uuenview can directly send encoded files by email or to the usenet. These messages are wrapped into a proper MIME envelope, which is handy if the recipient uses MIME-compliant mail or news software. OPTIONS
ENCODING SELECTION -b Chooses the Base64 encoding method as specified by the MIME standard. -u Chooses the uuencoding method, for compatibility with uuencode(1). -y Chooses the yEncoding method. -x Chooses the now obsolete xxencoding method. -t Sends the file(s) as plain text. -q Encodes the file(s) using quoted printable encoding. These options are positional and affect the encoding of all remaining files on the command line until changed. When sending, posting or attaching files, the default is to use Base64, resulting in MIME compliant messages. Otherwise, when encoding to standard output or into a file, the default is to use uuencoding. TARGETS -o Specifies that output shall be written into files. These files will have the same base name as the source file and an extension of .001, .002 etc, depending on the number of parts required by the -lines option. The encoded files are written to the current direc- tory. -od path Same as '-o', but the encoded files are written to the given directory instead. -m email Mails the encoded file(s), each one probably split into multiple parts, to the given email address. Multiple recipients can be given as a quoted, comma-separated list. On Unix systems, mail is usually piped to sendmail(8). -p newsgroup Posts the encoded file(s), each one probably split into multiple parts, to the given newsgroup. Multiple newsgroups can be given as a quoted, comma-separated list. The inews(1) program is invoked for posting. You may have to set the NNTPSERVER enviroment variable to your news server. -a Attaches files. This feature is expected to be used from shell scripts and the like. In attach mode, a message is read from standard input, complete with headers. The files given on the command line are then "attached" to the message, which is converted, if neces- sary, to a proper MIME multipart format. The -a option can be combined with -m or -p in order to directly mail or post the result. Else, the message, complete with attachments, is written to standard output. If no target option is given, the encoded data is printed to standard output. HEADERS When mailing or posting a file, it is possible to set certain headers. Be careful to quote parameters that consist of more than one word. -s subject Set the Subject: header line. The file name and part number are automatically appended. Without this, a default subject header is generated. -f from Set the From: header line. -r reply Set the Reply-To: header line. OTHER -v Verbosely prints everything the program's trying to do. -lines Substituting lines with a number, sets the maximum number of encoded lines per part. The encoded data is automatically split into as many parts as required. Line counts less than 200 are ignored. The uuencoding and xxencoding methods encode 45k, and Base64 encodes 57k of data in 1000 lines. If this option is not specified, the default is unlimited lines per part, resulting in exactly one part. file(s) One or more filenames to be processed. To encode a file from the standard input, use a single hyphen '-' and give a filename to be used for the encoded file as the next parameter. Options may also be set in the $UUENVIEW environment variable, which is read before processing the options on the command line. NOTES
Files read from standard input can only be used once, meaning that at most one target option may be given. Output written to standard output cannot be split into multiple parts. In this case, the -lines option is ignored. uuenview must be correctly configured at compile time in order for mailing and posting to work. If it doesn't, consult your system adminis- trator. The program used for posting a file can be set at runtime using the INEWS environment variable. This setting overrides the com- pile-time configuration. Base64 is not MIME. Base64 is the encoding specified by the MIME standard, but in order for a message to become a proper MIME message, a number of headers are required. uuenview produces these headers when mailing or posting, but not when writing to a file. In this case, uuenview does not have any control over the headers. If you include Base64 output into your messages, they are not MIME-compliant! If you rename, copy or link the program to uuencode, it may act as a smart replacement for the standard, accepting the same command-line syntax. This has not been well-tested yet. EXAMPLES
uuenview -m 'root,fred@somewhere.com' uudeview.tgz Encodes the file uudeview.tgz and mails it to both your local system administrator and to your friend Fred at the Somewhere company. If you give more than one filename on the command line, each file is usually handled separately. A workaround is to send them all as attachment to a single (or empty) mail: uuenview -m root -b -a file1 file2 < /dev/null Creates an empty mail and attaches the two given files, encoded in Base64 format, and mails the result to your system administrator. SEE ALSO
uudeview(1), uuencode(1), uudecode(1), sendmail(8), inews(1). The uudeview homepage on the Web, http://www.fpx.de/fp/Software/UUDeview/ BUGS
The program does not detect error conditions when mailing or posting. Attaching only works reliably if certain headers of the input message (for example Content-Type) are not folded and shorter than 1024 char- acters. It is not possible to encode into BinHex. The program will quite likely fail to handle binary data as input for plain text or quoted-printable attachments. On plain text attach- ments, the line length (must be less than 998 characters according to MIME) is not enforced. It is not possible to set the "charset" value of plain text attachments. It is not possible to set the content type value of attachments. sendmail(8) stops reading upon a line consisting only of a single dot. uudeview does not check plain text input files against this condi- tion. (The problem is worked around when using quoted-printable, and does not exist with the other encodings.) June 2001 UUENVIEW(1)
All times are GMT -4. The time now is 01:50 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy