This would be easier: While $PWDx has 3 slashes, take #?*/ off and put ...
something like
of course, quoting has to carry this all into PS1 for run time evaluation.
Last edited by DGPickett; 10-21-2010 at 05:16 PM..
Hello
I am using Debain Potato and I changed the PS1. When I log in locally everythink is fine, except that when I enter a long row without hitting enter, then it word wraps automatically. And it does it not at the end of the row, it does it in the middle of the row!
It also does not writes... (7 Replies)
I want to set my prompt to something more descriptive than a plain old $, so I set the PS1 variable as such:
PS1=""
Which changes the prompt correctly, but when I change directories, it does not update the prompt. So I tried this:
PS1="`pwd`>"
I get the same results when changing... (2 Replies)
can anyone tell me how to change the $ prompt by calling a variable.
Say for example i called a var 'enable' I and would like the $ prompt to change to a phrase like 'my prompt' any help would be great (1 Reply)
I know this question has come up before but I couldn't find any documentation on ksh here.
I'm trying
PS1="`whoami`@`hostname`:`pwd`> "
export PS1
in ksh but the working directory sticks at the home directory. How do I fix that? Also, how do I make the prompt bold in korn? (3 Replies)
I want to change the PS1 prompt with current time.
I want the PS1 to update for every one second.
I write a Script.
PS1='\T'
but it updates after i press enter key.I want to update without pressing enter key.
can any one help me? (0 Replies)
please advise what's wrong with this command ?
PS1="`hostname`:`who am i | cut -d " " -f1`:>>"
trying to make the PS1 prompt look like :
machine_name:username:>>
thank you (4 Replies)
I am 100% new to Unix and trying to learn.
This is my first time even touching a script in Unix.
We have the following variable script that I am trying to run....
##################################
###### variable test###
##################################
Hostname=`hostname`... (3 Replies)
I have coded PS1 as shown, producing the following result when writing on the command line
┌─ cdl
└──╼ make tracepdf2d
If I make an error in the command an ✗ is printed
┌─ ✗ cdl
└──╼ ls-a
ls-a: command not found
My problem is that if I just press enter, I do not want to have the... (3 Replies)
I have searched through google, and this forum to try and find the answer, but alas, nothing quite hits the whole answer.
I am trying to read the last line (or lines) of some log files. I do this often.
The files are named sequentially, using the date as part of the file name, and appending... (18 Replies)
Hello I am attempting to generate a bash scrip that prompts me at loggin to change my PS1 -
However, I am running into an issue w/ the code.
#!/bin/bash
#the point of this script is to that it automates and changes my prompts every day
msg1="What do you feel like adding today :"
echo... (11 Replies)
Discussion started by: D'go
11 Replies
LEARN ABOUT CENTOS
sasl_checkapop
sasl_checkapop(3) SASL man pages sasl_checkapop(3)NAME
sasl_checkapop - Check an APOP challenge/response
SYNOPSIS
#include <sasl/sasl.h>
int sasl_checkapop(sasl_conn_t *conn,
const char *challenge,
unsigned challen,
const char *response,
unsigned resplen);
DESCRIPTION
sasl_checkapop() will check an APOP challenge/response. APOP is an optional POP3 (RFC 1939) authentication command which uses a shared
secret (password). The password is stored in the SASL secrets database. For information on the SASL shared secrets database see the System
Administrators Guide in the doc/ directory of the SASL distribution.
If called with a NULL challenge, sasl_checkapop() will check to see if the APOP mechanism is enabled.
RETURN VALUE
sasl_checkapop returns an integer which corresponds to one of the following codes. SASL_OK indicates that the authentication is complete.
All other return codes indicate errors and should either be handled or the authentication session should be quit. See sasl_errors(3) for
meanings of return codes.
CONFORMING TO
RFC 4422, RFC 1939
SEE ALSO sasl(3), sasl_errors(3)SASL 29 June 2001 sasl_checkapop(3)