Sponsored Content
Full Discussion: Mail subject splitted
Operating Systems AIX Mail subject splitted Post 302955794 by Don Cragun on Monday 21st of September 2015 03:51:57 PM
Old 09-21-2015
So, knowing that things work after a reboot tells us that something was messed up in your environment. But, since you didn't show us the results until after you rebooted, we'll probably never know what was wrong. (It would have also been nice to know if logging out and logging back in would have solved your problem without rebooting.)

But, my best guesses would still be that either your IFS setting had been modified to include the double-quote character or that your PATH setting had been modified to find a different mail utility than the one you're now finding in /usr/bin.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Send a mail with a subject and an attachement

Dear All: I want to send a message to a list of people with a subject and an attachement, currently I am using the following command into a shell script: uuencode $FILENAME.gz $FILENAME.gz | mail john.kennedy@mycompany.com m.m@mycompany.com With this command I can send the message for a... (1 Reply)
Discussion started by: josecollantes
1 Replies

2. UNIX for Dummies Questions & Answers

Mail subject output of script

I am new to this site so please bear with my ignorances. I have started playing with mail on AIX 4.3.3 with many successes (thanks to this site) but am now stuck. I want to send a mail with the subject as the result of a script, eg. I want the mail body to read as the output from 'df -k... (4 Replies)
Discussion started by: kiano
4 Replies

3. UNIX for Dummies Questions & Answers

How to set Subject in 'mail' ?

Hi, I am trying to send some file to some mail ids using mail command in UNIX. Now the issue is I am not able to find how to add "Subject text" to the command. So I am using command like "mail abc@yahoo.com < file_name" Now if I use simple mail command I can set subject text by using... (2 Replies)
Discussion started by: hkapil
2 Replies

4. Shell Programming and Scripting

sort mail based on subject in unix.

Hi, I have a complicated requirement.I need to search for a particular pattern in the subject of incoming mail to a set of users and need to save the content of the mail in a file which will be uploaded to a file server. I have a perl script to do the upload.I need a script to sort the mail... (2 Replies)
Discussion started by: sriram.s
2 Replies

5. UNIX for Advanced & Expert Users

date need to be add in the subject of the mail.

Hi Am fetching a weekly report pf data..once i fetched the data i need a sent report by mail. In the subject of that mail i want to sent a message like.. SUBJECT :The report had been fetched from (01/12/08 to 07/12/08). I need to send a report like this every week with that particular... (2 Replies)
Discussion started by: bobprabhu
2 Replies

6. UNIX for Dummies Questions & Answers

mail -s not showing subject on emails

Hi, I have a cron job that creates backups nightly and sends me an email with output from the script. I'm recieving the email and the output; however, the subject field is always empty. Here is what I have in my crontab 00 23 * * * sh /test_backup/test_script | mail -s "Backups"... (2 Replies)
Discussion started by: orahi001
2 Replies

7. Shell Programming and Scripting

mail: subject and body text

HI, After giving the mail -e name@domain.com its asking the subject : after this its enter in to the body of the mail i.e. (in edit mode) How to end this edit process to send mail ? (2 Replies)
Discussion started by: thelakbe
2 Replies

8. Shell Programming and Scripting

adding hostname and date in subject of the mail

Hi Team, I coded my code to send mail to some reciepents with subject and date. Can somebody suggest me how to add host name to subject ? and the below code is correct for date ? my aim is to send mail with "subject in < hostname> on <date>".When i execute this script on my server its hung... (3 Replies)
Discussion started by: rocking77
3 Replies

9. Shell Programming and Scripting

Subject line missing while sending mail

Hi, I have below script PROJECT_NAME=UDL/UDL_Weekly sub= echo ${PROJECT_NAME}|cut -d "/" -f2 cat pr.sh|mail -s "`hostname`: $sub failed" sonu.pal@xyz.com While running the script I am receiving the subject line in mail as " podetlsapp01: failed' instead of " podetlsapp01: ... (1 Reply)
Discussion started by: sonu_pal
1 Replies

10. Shell Programming and Scripting

Grep the last line and put on mail subject

I have mail: cat /home/oracle/scripts/dbsizedaily.txt | mail -s "$TODAY: PROD DB Size" $RECIPIENTS I like to get and put USED_GB and %USED of the very last row from /home/oracle/scripts/dbsizedaily.txt. /home/oracle/scripts/dbsizedaily.txt has : DATE TIME TOTAL_GB USED_GB ... (6 Replies)
Discussion started by: Daniel Gate
6 Replies
SU(1)								   User Commands							     SU(1)

NAME
su - change user ID or become superuser SYNOPSIS
su [options] [username] DESCRIPTION
The su command is used to become another user during a login session. Invoked without a username, su defaults to becoming the superuser. The optional argument - may be used to provide an environment similar to what the user would expect had the user logged in directly. Additional arguments may be provided after the username, in which case they are supplied to the user's login shell. In particular, an argument of -c will cause the next argument to be treated as a command by most command interpreters. The command will be executed by the shell specified in /etc/passwd for the target user. You can use the -- argument to separate su options from the arguments supplied to the shell. The user will be prompted for a password, if appropriate. Invalid passwords will produce an error message. All attempts, both valid and invalid, are logged to detect abuse of the system. The current environment is passed to the new shell. The value of $PATH is reset to /bin:/usr/bin for normal users, or /sbin:/bin:/usr/sbin:/usr/bin for the superuser. This may be changed with the ENV_PATH and ENV_SUPATH definitions in /etc/login.defs. A subsystem login is indicated by the presence of a "*" as the first character of the login shell. The given home directory will be used as the root of a new file system which the user is actually logged into. OPTIONS
The options which apply to the su command are: -c, --command COMMAND Specify a command that will be invoked by the shell using its -c. The executed command will have no controlling terminal. This option cannot be used to execute interractive programs which need a controlling TTY. -, -l, --login Provide an environment similar to what the user would expect had the user logged in directly. When - is used, it must be specified as the last su option. The other forms (-l and --login) do not have this restriction. -s, --shell SHELL The shell that will be invoked. The invoked shell is chosen from (highest priority first): The shell specified with --shell. If --preserve-environment is used, the shell specified by the $SHELL environment variable. The shell indicated in the /etc/passwd entry for the target user. /bin/sh if a shell could not be found by any above method. If the target user has a restricted shell (i.e. the shell field of this user's entry in /etc/passwd is not listed in /etc/shells), then the --shell option or the $SHELL environment variable won't be taken into account, unless su is called by root. -m, -p, --preserve-environment Preserve the current environment, except for: $PATH reset according to the /etc/login.defs options ENV_PATH or ENV_SUPATH (see below); $IFS reset to "<space><tab><newline>", if it was set. If the target user has a restricted shell, this option has no effect (unless su is called by root). Note that the default behavior for the environment is the following: The $HOME, $SHELL, $USER, $LOGNAME, $PATH, and $IFS environment variables are reset. If --login is not used, the environment is copied, except for the variables above. If --login is used, the $TERM, $COLORTERM, $DISPLAY, and $XAUTHORITY environment variables are copied if they were set. Other environments might be set by PAM modules. CAVEATS
This version of su has many compilation options, only some of which may be in use at any particular site. CONFIGURATION
The following configuration variables in /etc/login.defs change the behavior of this tool: CONSOLE_GROUPS (string) List of groups to add to the user's supplementary groups set when logging in on the console (as determined by the CONSOLE setting). Default is none. Use with caution - it is possible for users to gain permanent access to these groups, even when not logged in on the console. DEFAULT_HOME (boolean) Indicate if login is allowed if we can't cd to the home directory. Default is no. If set to yes, the user will login in the root (/) directory if it is not possible to cd to her home directory. ENV_PATH (string) If set, it will be used to define the PATH environment variable when a regular user login. The value is a colon separated list of paths (for example /bin:/usr/bin) and can be preceded by PATH=. The default value is PATH=/bin:/usr/bin. ENV_SUPATH (string) If set, it will be used to define the PATH environment variable when the superuser login. The value is a colon separated list of paths (for example /sbin:/bin:/usr/sbin:/usr/bin) and can be preceded by PATH=. The default value is PATH=/sbin:/bin:/usr/sbin:/usr/bin. SULOG_FILE (string) If defined, all su activity is logged to this file. SU_NAME (string) If defined, the command name to display when running "su -". For example, if this is defined as "su" then a "ps" will display the command is "-su". If not defined, then "ps" would display the name of the shell actually being run, e.g. something like "-sh". SYSLOG_SU_ENAB (boolean) Enable "syslog" logging of su activity - in addition to sulog file logging. FILES
/etc/passwd User account information. /etc/shadow Secure user account information. /etc/login.defs Shadow password suite configuration. EXIT VALUES
On success, su returns the exit value of the command it executed. If this command was terminated by a signal, su returns the number of this signal plus 128. If su has to kill the command (because it was asked to terminate, and the command did not terminate in time), su returns 255. Some exit values from su are independent from the executed command: 0 success (--help only) 1 System or authentication failure 126 The requested command was not found 127 The requested command could not be executed SEE ALSO
login(1), login.defs(5), sg(1), sh(1). shadow-utils 4.1.5.1 05/25/2012 SU(1)
All times are GMT -4. The time now is 01:44 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy