Re: compiling elog 2.6.1 on solaris platform, posted by Steve Jones on Wed Feb 8 18:19:02 2006
|
| Stefan Ritt wrote: |
| Steve Jones wrote: | | I have checked and can find no reference within Sun documents regarding the support of the forkpty() function. I have not been following elog development lately -- what is shell substitution supposed to buy us? |
See the config manual and look for $shell |
| Steve Jones wrote: | | Yep, I saw it. Thanks |
|
Work on PAM Support?, posted by Steve Jones on Wed Feb 8 18:23:52 2006
|
Stefan (or any others):
Has anyone been seriously looking into building in PAM support in eLog? I ask because I have started reading the developer papers from Sun and looking at sample code.
Thanks
Steve |
|
Re: compiling elog 2.6.1 on solaris platform, posted by Steve Jones on Wed Feb 8 18:34:43 2006
|
| Steve Jones wrote: |
| Stefan Ritt wrote: |
| Steve Jones wrote: | | I have checked and can find no reference within Sun documents regarding the support of the forkpty() function. I have not been following elog development lately -- what is shell substitution supposed to buy us? |
See the config manual and look for $shell |
| Steve Jones wrote: | | Yep, I saw it. Thanks |
|
| Steve Jones wrote: |
Stefan, I found the following "forkpty()" replacement for running under Solaris. The URL is http://www.developerweb.net/forum/showthread.php?t=2990.
Perhaps this can be used unless someone comes up with a Solaris "util" library.
#ifdef SOLARIS /* Use the code in my_forkpty.c */
int my_forkpty (int *amaster, char *name, void *unused1, void *unused2);
#define forkpty my_forkpty
#endif
-----------------------
my_forkpty.c
-----------------------
#include <fcntl.h>
#include <unistd.h>
#include <stdlib.h>
#include <sys/ioctl.h>
#include <sys/stream.h>
#include <sys/stropts.h>
/* fork_pty() remplacement for Solaris.
* This ignore the last two arguments
* for the moment
*/
int
my_forkpty (int *amaster,
char *name,
void *unused1,
void *unused2)
{
int master, slave;
char *slave_name;
pid_t pid;
master = open("/dev/ptmx", O_RDWR);
if (master < 0)
return -1;
if (grantpt (master) < 0)
{
close (master);
return -1;
}
if (unlockpt (master) < 0)
{
close (master);
return -1;
}
slave_name = ptsname (master);
if (slave_name == NULL)
{
close (master);
return -1;
}
slave = open (slave_name, O_RDWR);
if (slave < 0)
{
close (master);
return -1;
}
if (ioctl (slave, I_PUSH, "ptem") < 0
|| ioctl (slave, I_PUSH, "ldterm") < 0)
{
close (slave);
close (master);
return -1;
}
if (amaster)
*amaster = master;
if (name)
strcpy (name, slave_name);
pid = fork ();
switch (pid)
{
case -1: /* Error */
return -1;
case 0: /* Child */
close (master);
dup2 (slave, STDIN_FILENO);
dup2 (slave, STDOUT_FILENO);
dup2 (slave, STDERR_FILENO);
return 0;
default: /* Parent */
close (slave);
return pid;
}
return -1;
}
|
|
|
Re: email problems, posted by Chris Warner on Wed Feb 8 18:38:30 2006
|
The email address id correct. I am using an Elog Binary. I don't have the source code .
Chris Warner
| Stefan Ritt wrote: |
| Chris Warner wrote: | Error sending Email via "xxx.xxx.xxx.xx": Syntax error, parameters in command "MAIL FROM: christopher_warner@xxx.gov SIZE=1985" unrecognized or missing
|
There are two possible reasons:
1) The email address "christopher_warner@xxx.gov" is invalid. Some SMTP server immediately complain about invalid email addresses and refuse to send any mail then. In that case just supply an existing email address or remove that test account.
2) The SMTP server does not like the "SIZE=xxx" option. This comes from a single line in elogd.c:
snprintf(str, strsize - 1, "MAIL FROM: %s SIZE=%d\r\n", from, strlen(text));
you could just go there and remove the " SIZE=%d", so that the line looks like:
snprintf(str, strsize - 1, "MAIL FROM: %s\r\n", from);
to see if that makes any difference. |
|
menu commands - user list does not match config list, posted by Alan Stone on Thu Feb 9 00:37:29 2006
|
I am attempting to configure the Elog for use at the CMS Remote Operations Center
at Fermilab. I included the following option:
Menu commands = List, New, Reply, Duplicate, Find, Last day, Config, Admin, Login, Logout, Help
but the available list (after restarting the elog daemon) gives me:
CMS ROC Logbook, Page 1 of 1 Logged in as "Alan Stone" ELOG Home
New | Find | Select | CSV Import | Config | Logout | Help
Did I miss a step in the syntax instructions?
Thanks, Alan |
|
Re: menu commands - user list does not match config list, posted by Stefan Ritt on Thu Feb 9 09:04:05 2006
|
| Alan Stone wrote: | I am attempting to configure the Elog for use at the CMS Remote Operations Center
at Fermilab. I included the following option:
Menu commands = List, New, Reply, Duplicate, Find, Last day, Config, Admin, Login, Logout, Help
but the available list (after restarting the elog daemon) gives me:
CMS ROC Logbook, Page 1 of 1 Logged in as "Alan Stone" ELOG Home
New | Find | Select | CSV Import | Config | Logout | Help
Did I miss a step in the syntax instructions? |
Yap. There are two menus, one for the listing page which contains only line per entry, and one for the individual entry page. You changed the one for the individual entry page, which you will see when you slick on any entry. To change the listing page manu, do a List Menu commands = ... |
|
Re: email problems, posted by Stefan Ritt on Thu Feb 9 09:09:30 2006
|
| Chris Warner wrote: | | The email address id correct. I am using an Elog Binary. I don't have the source code. |
Ok, so I removed the SIZE=xxx parameter, which is not strictly necessary anyhow I believe. So wait for the next release, and you can try. |
|
Re: Work on PAM Support?, posted by Stefan Ritt on Thu Feb 9 09:12:44 2006
|
| Steve Jones wrote: | | Has anyone been seriously looking into building in PAM support in eLog? I ask because I have started reading the developer papers from Sun and looking at sample code. |
Not really. I have two big issues higher on my list: XML database format and multithreaded HTTP server. From having a quick look to PAM, I was not sure how easy this would be to implement. If it's not too difficult, it could move higher in the priority list. |
|