search for: _3_

...-107,8 +107,8 @@ main (int argc, char *argv[]) } /* Close the write side of the pipe. This should cause guestunmount - * to exit. It should exit with status code _2_ because we gave it - * a mountpoint which isn't a FUSE mountpoint. + * to exit. It should exit with status code _3_ because we gave it + * a directory which isn't a FUSE mountpoint. */ close (pipefd[1]); @@ -117,10 +117,10 @@ main (int argc, char *argv[]) perror ("waitpid"); exit (EXIT_FAILURE); } - if (!WIFEXITED (status) || WEXITSTATUS (status) != 2) { + if (!WIFEXITED (...

This is what I'm seeing on my DHCP server: # tcpdump -i eth0 -vvv -s 1500 '(port 67 or port 68)' tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 1500 bytes 13:24:05.679950 IP (tos 0x0, ttl? 20, id 0, offset 0, flags [none], proto: UDP (17), length: 576) 0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Request from 00:24:54:d9:d4:2f (oui

On Wed, 2014-03-05 at 13:18 -0500, Gene Cumm wrote: > Second, I notice the Altiris server specifies _3_ options of code 43, > including one of length 253. The pack/unpack _should_ handle this but > may split it differently. That's legal, and treated as if the values had been concatenated. See RFC2131, section 4.1, and particularly the second paragraph on page 24. Unfortunately, a lot of...

...e: > This is what I'm seeing on my DHCP server: Any chance you could sent that as a pcap file (I'd recommend classic pcap not pcap-ng and then gzip it to give a little semblance of integrity checking)? Feel free to send it to me directly. Second, I notice the Altiris server specifies _3_ options of code 43, including one of length 253. The pack/unpack _should_ handle this but may split it differently. -- -Gene

On Thu, Mar 6, 2014 at 11:20 AM, Jeffrey Hutzelman <jhutz at cmu.edu> wrote: > On Wed, 2014-03-05 at 13:18 -0500, Gene Cumm wrote: > >> Second, I notice the Altiris server specifies _3_ options of code 43, >> including one of length 253. The pack/unpack _should_ handle this but >> may split it differently. > > That's legal, and treated as if the values had been concatenated. See I never said that it was against the RFC. I was merely stating the level of f...

On Fri, May 09, 2014 at 09:08:56PM -0400, Waiman Long wrote: > On 05/08/2014 03:04 PM, Peter Zijlstra wrote: > >On Wed, May 07, 2014 at 11:01:36AM -0400, Waiman Long wrote: > >> /* > >>+ * To have additional features for better virtualization support, it is > >>+ * necessary to store additional data in the queue node structure. So > >>+ * a new queue

On Fri, May 09, 2014 at 09:08:56PM -0400, Waiman Long wrote: > On 05/08/2014 03:04 PM, Peter Zijlstra wrote: > >On Wed, May 07, 2014 at 11:01:36AM -0400, Waiman Long wrote: > >> /* > >>+ * To have additional features for better virtualization support, it is > >>+ * necessary to store additional data in the queue node structure. So > >>+ * a new queue

...t, etc... servers) /var/www (web servers) /var/ftp (FTP servers) In some cases -- FHS 2.3+ compliant -- these are under /srv instead of /var. If I want local data/temporary storage, I typically create of the "discretionary" size: /export|home/(systemname) I like to make at least _3_ "discretionary" size, 2 mounted with 1 spare, so 1/3rd each. Again, in the day of LVM/LVM2, I typically just reserve 15-30% of the disk allocation instead of making pre-made spares of each class -- but I would at least make _2_ "discretionary" size (instead of one big one). I...