search for: nfailed

Displaying 10 results from an estimated 10 matches for "nfailed".

Did you mean: failed
2011 Sep 06
2
scim-bridge?
Anybody familiar with it, or what it's needed for? I've got at least one user (it's *very* noticeable with her) whose system is spamming /var/log/messages, to the effect of "Another agent is running...\nFailed to allocate the agent. Exitting" (complete with misspelled exiting). In googling, I've seen someone just removing the package. What, if anything, would that break? Oh, right, CentOS 5.6, KDE 3.5.4-1 mark
2015 Jan 15
0
PXE Error Reporting
....x. > > the one from Fedora 20, syslinux-4.05. > > It turns out that pxelinux.0 from Fedora 21, syslinux-6.03, reports > "Failed to load ldlinux.c32" when ldlinux.c32 can't be read, and LDLINUX is special: core/elflink/load_env32.c 170:out: 171: writestr("\nFailed to load "); 172: writestr(LDLINUX); > "Loading <FILE>... failed: No such file or directory" when the TFTP > server replies with "Permission denied" for the kernel or initrd. open() returns ENOENT for all errors: com32/lib/sys/open.c 68: handle = open_...
2008 Mar 12
1
deliver fails - passdb doesn't support lookups?
Hello, I'm trying to get `deliver` (the LDA) to function properly. I can get it to work without doing a user lookup, but for my own sense of sanity, I want to know what I'm doing wrong getting user lookups working. (I'm using dovecot 1.0.10). Here's what I have in the "auth default" section: auth default { mechanisms = plain login passdb ldap
2015 Jan 15
3
PXE Error Reporting
Sebastian, On 01/15/2015 12:49 AM, Sebastian Herbszt wrote: > which version of pxelinux were you trying? Looks like < 5.x. the one from Fedora 20, syslinux-4.05. It turns out that pxelinux.0 from Fedora 21, syslinux-6.03, reports "Failed to load ldlinux.c32" when ldlinux.c32 can't be read, and "Loading <FILE>... failed: No such file or directory" when the
2012 Oct 19
3
[PATCH 0/3] elflink fixes
From: Matt Fleming <matt.fleming at intel.com> The first two patches in this series are fixes for bugs reported by someone in #syslinux. The third makes dmitest.c32 actually wait for user input. If no one has any objections/concerns, I'll pull this into the official elflink branch. Matt Fleming (3): core: Print error message if we don't load ldlinux.c32 Clean up $(GPLLIB) leak
2013 Jun 12
3
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
On Wed, 12 Jun, at 11:17:44AM, Gerardo Exequiel Pozzi wrote: > Cool thanks!. Now looks better, but still not work. > > For some reason, "ldlinux.c32" is apparently sent but "Failed to load" > by PXELINUX and few seconds later, dnsmasq shows an error message > "failed sending": Argh! The patch was broken. I missed the new core/path.c file. My bad.
2013 Jun 12
5
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
...t allocate memory for PATH\n"); - goto out; - } - - strcat(PATH, ":"); - strcat(PATH, path); + if (!path_add(path)) { + printf("Couldn't allocate memory for PATH\n"); + goto out; } start_ldlinux(1, argv); } out: - free(PATH); writestr("\nFailed to load ldlinux.c32"); } diff --git a/core/fs/fs.c b/core/fs/fs.c index 1cb4b00..b6ee19c 100644 --- a/core/fs/fs.c +++ b/core/fs/fs.c @@ -10,8 +10,6 @@ #include "fs.h" #include "cache.h" -__export char *PATH; - /* The currently mounted filesystem */ __export struct...
2013 Jun 12
0
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
...t allocate memory for PATH\n"); - goto out; - } - - strcat(PATH, ":"); - strcat(PATH, path); + if (!path_add(path)) { + printf("Couldn't allocate memory for PATH\n"); + goto out; } start_ldlinux(1, argv); } out: - free(PATH); writestr("\nFailed to load ldlinux.c32"); } diff --git a/core/fs/fs.c b/core/fs/fs.c index 1cb4b00..b6ee19c 100644 --- a/core/fs/fs.c +++ b/core/fs/fs.c @@ -10,8 +10,6 @@ #include "fs.h" #include "cache.h" -__export char *PATH; - /* The currently mounted filesystem */ __export struct...
2013 Jun 11
2
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
On Mon, 10 Jun, at 07:57:50AM, H. Peter Anvin wrote: > Either that or make the path a list rather than a string, using the > normal word separators when entered on the command line, a bit like the > (t)csh does. That is a bigger change but is probably a better solution. How would this solution handle filenames containing spaces? Would we need to escape (presumably with a backslash)
2013 Jun 12
0
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
...- strcat(PATH, ":"); > - strcat(PATH, path); > + if (!path_add(path)) { > + printf("Couldn't allocate memory for PATH\n"); > + goto out; > } > > start_ldlinux(1, argv); > } > > out: > - free(PATH); > writestr("\nFailed to load ldlinux.c32"); > } > > diff --git a/core/fs/fs.c b/core/fs/fs.c > index 1cb4b00..b6ee19c 100644 > --- a/core/fs/fs.c > +++ b/core/fs/fs.c > @@ -10,8 +10,6 @@ > #include "fs.h" > #include "cache.h" > > -__export char *PATH; &gt...